Skip to content

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

Merged
merged 1 commit into from
Jun 22, 2025
Merged

Fix limit in subqueries #1899

merged 1 commit into from
Jun 22, 2025

Conversation

Dimchikkk
Copy link
Contributor

@Dimchikkk Dimchikkk commented Jun 20, 2025

The bug was introduced in #1793 I think.

@iffyio iffyio changed the title fix limit in subqueries Fix limit in subqueries Jun 22, 2025
Copy link
Contributor

@iffyio iffyio left a 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

@iffyio iffyio merged commit 7865de0 into apache:main Jun 22, 2025
10 checks passed
@Dimchikkk
Copy link
Contributor Author

@iffyio Thanks for merging.
@alamb Could this fix be backported to 0.56, or will DataFusion move straight to 0.57?

@alamb
Copy link
Contributor

alamb commented Jun 22, 2025

@iffyio Thanks for merging. @alamb Could this fix be backported to 0.56, or will DataFusion move straight to 0.57?

DataFusion hasn't updated to 0.56 yet

Also, we haven't completed releasing 0.57.0 yet:

Maybe we should make a new release candidate for 0.57? Or make a fast 0.58 release?

@iffyio
Copy link
Contributor

iffyio commented Jun 22, 2025

Ah yeah a new release candidate sounds reasonable given 0.57 isn't out yet

@Dimchikkk
Copy link
Contributor Author

@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)?

@alamb
Copy link
Contributor

alamb commented Jun 23, 2025

@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?

Ah yeah a new release candidate sounds reasonable given 0.57 isn't out yet

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 ?

@alamb
Copy link
Contributor

alamb commented Jun 23, 2025

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

@Dimchikkk
Copy link
Contributor Author

Dimchikkk commented Jun 28, 2025

@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?

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Parse error for limit in subqueries
3 participants