HIVE-28725: Sorting is performed when order by position is disabled when CBO is enabled #5623
+595
−11
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.
What changes were proposed in this pull request?
HiveSortLimit
operator whenhive.orderby.position.alias
is disabled and theOrder by
clause of the query has integer constants as keys. Also ignore the constants as keys when there are both column references and constant keys.HiveSortExchange
operator when both field collaction and distribution keys are all constants andhive.orderby.position.alias
is disabled. Also ignore the constants as keys when there are both column references and constant keys.Why are the changes needed?
To synchronize the Order/Sort/Distribute/Cluster by behaviors when
hive.orderby.position.alias
is disabled and CBO is enabled/disabled .Does this PR introduce any user-facing change?
Yes, the results of queries with Order/Sort/Cluster by clauses may have different order.
Is the change a dependency upgrade?
No.
How was this patch tested?