You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Takeshi Yamamuro (Jira)" <ji...@apache.org> on 2020/09/30 12:39:00 UTC
[jira] [Resolved] (SPARK-32741) Check if the same ExprId refers to
the unique attribute in logical plans
[ https://issues.apache.org/jira/browse/SPARK-32741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Takeshi Yamamuro resolved SPARK-32741.
--------------------------------------
Fix Version/s: 3.1.0
Assignee: Takeshi Yamamuro
Resolution: Fixed
Resolved by https://github.com/apache/spark/pull/29585
> Check if the same ExprId refers to the unique attribute in logical plans
> ------------------------------------------------------------------------
>
> Key: SPARK-32741
> URL: https://issues.apache.org/jira/browse/SPARK-32741
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.1.0
> Reporter: Takeshi Yamamuro
> Assignee: Takeshi Yamamuro
> Priority: Major
> Fix For: 3.1.0
>
>
> Some plan transformations (e.g., `RemoveNoopOperators`) implicitly assume the same `ExprId` refers to the unique attribute. But, `RuleExecutor` does not check this integrity between logical plan transformations. So, this ticket targets at adding this check in `isPlanIntegral` of `Analyzer`/`Optimizer`.
> This PR comes from the talk with @cloud-fan @viirya in https://github.com/apache/spark/pull/29485#discussion_r475346278
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org