[
https://issues.apache.org/jira/browse/SPARK-54075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18033872#comment-18033872
]
Dongjoon Hyun commented on SPARK-54075:
---------------------------------------
Hi, [~mihailoale-db] .
Apache Spark community has a policy which manages `Fix Version` and `Target
Version` like the following. So, please don't set it when you file a JIRA issue.
- https://spark.apache.org/contributing.html
{quote}Do not set the following fields:
- Fix Version. This is assigned by committers only when resolved.
- Target Version. This is assigned by committers to indicate a PR has been
accepted for possible fix by the target version.
{quote}
> 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
> Priority: Major
> Labels: pull-request-available
>
> 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]
