[BUG] Asc/desc hotfix for range partitioning #1829
Assignees
Comments
clarkzinzow
added a commit
that referenced
this issue
Feb 14, 2024
…for range partitioning and sorting. (#1862) This PR ensures that we properly track ascending/descending sort order for range partitioning and sorting ops, to ensure that downstream operations correctly interpret the partition spec. For example, before this PR, the planner would always assume that if both sides of the join are sorted, then they're sorted in ascending order and could therefore be efficiently joined with our sort-merge join (which currently only does ascending-order sorts/merges); this would lead to incorrect results if either side was sorted in descending order. Closes #1829 ## Follow-ups (future PRs) - Refactor sort-merge join to work for both ascending and descending order; this can be done when porting the `Partitioning` abstraction to Rust to enable better dtype support.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: