fix(cubesql): Fix SortPushDown pushing sort through joins #9464
Conversation
This file contains 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
LogicalPlan::Join and CrossJoin do not preserve the ordering semantically When planned as HashJoin it will output batches in same order as they are coming from right stream But both Join and CrossJoin will have same partitioning as right input (even when repartition_joins disabled), and these partitions can be collected in arbitrary order by CoalescePartitions Also, Substrait says that for both Join and Cross Product > Orderedness is empty post operation See https://substrait.io/relations/logical_relations/#join-operation
mcheshkov
changed the title
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #9464 +/- ##
==========================================
- Coverage 83.89% 76.54% -7.36%
==========================================
Files 229 400 +171
Lines 83544 104866 +21322
Branches 0 3723 +3723
==========================================
+ Hits 70087 80265 +10178
- Misses 13457 24169 +10712
- Partials 0 432 +432
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
Check List
Description of Changes Made (if issue reference is not provided)
LogicalPlan::JoinandCrossJoindo not preserve the ordering semanticallyWhen planned as
HashJoinit will output batches in same order as they are coming from right streamBut both
JoinandCrossJoinwill have same partitioning as right input (even whenrepartition_joinsdisabled), and these partitions can be collected in arbitrary order byCoalescePartitionsSide note: Substrait says that for both Join and Cross Product
See https://substrait.io/relations/logical_relations/#join-operation