[
https://issues.apache.org/jira/browse/SPARK-51474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
L. C. Hsieh resolved SPARK-51474.
---------------------------------
Fix Version/s: 4.1.0
Resolution: Fixed
Issue resolved by pull request 50239
[https://github.com/apache/spark/pull/50239]
> Don't insert redundant ColumnarToRowExec for node supporting both columnar
> and row output
> -----------------------------------------------------------------------------------------
>
> Key: SPARK-51474
> URL: https://issues.apache.org/jira/browse/SPARK-51474
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 4.0.0
> Reporter: L. C. Hsieh
> Assignee: L. C. Hsieh
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.1.0
>
>
> There is a corner case in ApplyColumnarRulesAndInsertTransitions. When a plan
> required to output rows, if the node supports both columnar and row output,
> the rule currently adds a redundant ColumnarToRowExec to its upstream. This
> ColumnarToRowExec is redundant and unnecessary.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
