You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "L. C. Hsieh (Jira)" <ji...@apache.org> on 2025/03/11 20:26:00 UTC
[jira] [Assigned] (SPARK-51474) Don't insert redundant ColumnarToRowExec for node supporting both columnar and row output
[ https://issues.apache.org/jira/browse/SPARK-51474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
L. C. Hsieh reassigned SPARK-51474:
-----------------------------------
Assignee: L. C. Hsieh
> 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
>
> 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-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org