Fix None Projections in Projection Pushdown #9005
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
core
| ---- | ||
|
|
||
| statement ok | ||
| set datafusion.optimizer.max_passes=1; |
Contributor
There was a problem hiding this comment.
As far as I remember default value is 3. It is better to restore it 3.
5 tasks
Member
|
Thank you! @berkaysynnada |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Closes #9004.
Rationale for this change
When source projections are none, it means it projects all columns in its file schema. This case was not properly handled.
What changes are included in this PR?
Replace None's with all indices in file schema.
Are these changes tested?
Yes, an slt test is added similar to the one in the issue.
Are there any user-facing changes?