[
https://issues.apache.org/jira/browse/SPARK-34593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17319553#comment-17319553
]
Apache Spark commented on SPARK-34593:
--------------------------------------
User 'cloud-fan' has created a pull request for this issue:
https://github.com/apache/spark/pull/32132
> Preserve broadcast nested loop join output partitioning and ordering
> --------------------------------------------------------------------
>
> Key: SPARK-34593
> URL: https://issues.apache.org/jira/browse/SPARK-34593
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 3.2.0
> Reporter: Cheng Su
> Assignee: Cheng Su
> Priority: Minor
> Fix For: 3.2.0
>
>
> `BroadcastNestedLoopJoinExec` does not preserve `outputPartitioning` and
> `outputOrdering` right now. But it can preserve the streamed side
> partitioning and ordering when possible. This can help avoid shuffle and sort
> in later stage, if there's join and aggregation in the query.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
