fix: substrait limit when fetch is None #7669
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
Signed-off-by: Ruihang Xia <[email protected]>
github-actions
bot
added
core
alamb
approved these changes
Sep 28, 2023
|
|
||
| match &poll { | ||
| Poll::Ready(Some(Ok(batch))) => { | ||
| if batch.num_rows() > 0 && self.skip == 0 { |
There was a problem hiding this comment.
Is the rationale that this condition is redundant because any batch with zero rows will also have self.skip equal to zero?
There was a problem hiding this comment.
Yes. To my understanding these two conditions are identical. So I removed one to make it simpler
Ted-Jiang
pushed a commit
to Ted-Jiang/arrow-datafusion
that referenced
this pull request
Oct 7, 2023
* fix: substrait limit when fetch is None Signed-off-by: Ruihang Xia <[email protected]> * Add comments --------- Signed-off-by: Ruihang Xia <[email protected]> Co-authored-by: Andrew Lamb <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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?
related to GreptimeTeam/greptimedb#2495
Rationale for this change
I found the producer will replace
fetch = Nonewithfetch = 0, and consumer will always putSomein the position of fetch. This is incorrect for query withoutLIMIT, e.g.:SELECT * FROM t OFFSET 1What changes are included in this PR?
Fix the bug. As substrait cannot express
None, I useusize::MAXto representNonein producer, and convert it back toNonein consumer.This patch also has a minor change in
LimitExec. I thought that condition was redundant so I removed it.Are these changes tested?
I add a new round trip case
Are there any user-facing changes?
No