[
https://issues.apache.org/jira/browse/SPARK-35760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Takeshi Yamamuro resolved SPARK-35760.
--------------------------------------
Fix Version/s: 3.2.0
Assignee: Cheng Su
Resolution: Fixed
Resolved by https://github.com/apache/spark/pull/32911
> Fix the max rows check for broadcast exchange
> ---------------------------------------------
>
> Key: SPARK-35760
> URL: https://issues.apache.org/jira/browse/SPARK-35760
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.2.0
> Reporter: Cheng Su
> Assignee: Cheng Su
> Priority: Minor
> Fix For: 3.2.0
>
>
> This is to fix the maximal allowed number of rows check in
> `BroadcastExchangeExec`. After [https://github.com/apache/spark/pull/27828,]
> the max number of rows is calculated based on max capacity of
> `BytesToBytesMap` (previous value before the PR is 512000000). This
> calculation is not accurate as only `UnsafeHashedRelation` is using
> `BytesToBytesMap`. `LongHashedRelation` (used for broadcast join on key with
> long data type) has limit of 512000000
> ([https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/execution/joins/HashedRelation.scala#L584]
> ), and `BroadcastNestedLoopJoinExec` is not depending on `HashedRelation` at
> all.
--
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
