-
Notifications
You must be signed in to change notification settings - Fork 619
Fix limit
in subqueries
#1899
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix limit
in subqueries
#1899
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks @Dimchikkk!
cc @alamb
Ah yeah a new release candidate sounds reasonable given 0.57 isn't out yet |
@alamb I'm aware that DataFusion isn’t on 0.56 yet. However, in order to upgrade it to 0.56, this fix would need to be backported. So I’m wondering: what’s the plan? Will this fix be backported to 0.56, or is DataFusion planning to skip 0.56 and move directly to 0.57 (or beyond)? |
@Dimchikkk I don't have a plan myself -- I think it will be driven by someone who needs features of sqlparser in a new version of DataFusion. Perhaps you can help out and make a PR to upgrade?
I just completed the release of 0.57.0 given that each release takes a while to complete: I would be happy to accelerate the timeline for 0.58.0 if that is helpful. Perhaps I can start making another release today / tomorrow? What do you think @Dimchikkk and @iffyio ? |
I didn't hold 0.57.0 as the bug wasn't introduced in 0.57.0 -- instead it seems to have been introduced in 0.56.0 -- so in my mind it makes sense to just keep pushing forward with the releases |
@alamb yeah, I have a PR for 0.56 here: apache/datafusion#16456, but it requires the current fix and #1905 to be backported to 0.56. |
limit
in subqueries #1898.The bug was introduced in #1793 I think.