Add rule to eliminate LIMIT 0
and replace it with an EmptyRelation
#213
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 #206
Rationale for this change
LIMIT 0
can be used to test a certain query / get the schema from a query or the value0
can result from a constant folding. This rule replaces the limit 0 by an empty plan, saving time in the physical planner (no need to read metadata/statistics/partitions etc) and there is no need to produce a single batch.What changes are included in this PR?
A new optimization pass to replace
LIMIT 0
in theLogicalPlan
with anEmptyRelation
, with the same schema.Are there any user-facing changes?
No breaking changes, should only be faster in some cases.