[
https://issues.apache.org/jira/browse/SPARK-54075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dongjoon Hyun resolved SPARK-54075.
-----------------------------------
Fix Version/s: 4.1.0
Resolution: Fixed
Issue resolved by pull request 52779
[https://github.com/apache/spark/pull/52779]
> Make ResolvedCollation evaluable
> --------------------------------
>
> Key: SPARK-54075
> URL: https://issues.apache.org/jira/browse/SPARK-54075
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 4.1.0
> Reporter: Mihailo Aleksic
> Assignee: Mihailo Aleksic
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.1.0
>
>
> In this PR I propose to make ResolvedCollation evaluable. By making
> ResolvedCollation evaluable, it can now pass the canEvaluateWithinJoin check,
> allowing the optimizer to use efficient hash joins for queries with inline
> COLLATE in join conditions (before this change we would fallback to
> BroadcastNestedLoopJoin).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
