Fix #6184: skip unused column removal right after a filter with entries in the projection map #6221
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.
Fixes #6184
The subquery flattener inserted a filter with entries in the
projection_map
when using aLIMIT
in a correlated subquery. Normally entries in theprojection_map
are only added after theRemoveUnusedColumns
optimizer is called (by a different optimizer) - and the optimizer did not correctly take these entries into account. This PR fixes the issue by skipping pruning of columns under a filter with entries set in theprojection_map
.