Update DataFusion to 52.2, remove LimitPushdown workaround#882
Merged
madesroches merged 4 commits intomainfrom Mar 2, 2026
Merged
Update DataFusion to 52.2, remove LimitPushdown workaround#882madesroches merged 4 commits intomainfrom
madesroches merged 4 commits intomainfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
LimitPushdownphysical optimizer workaround in datafusion-wasm — the upstream bug is fixed in 52.2 (fix: The limit_pushdown physical optimization rule removes limits in some cases leading to incorrect results apache/datafusion#20048)SessionStateBuilder,PhysicalOptimizer, andPhysicalOptimizerRuleimportsCloses #809
Test plan
cargo test— all workspace tests passwasm-pack test --headless --firefox— all 20 WASM tests pass, includingtest_dictionary_projection_limitwhich validates LIMIT works correctly without the workaround