You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Xi Liang (Jira)" <ji...@apache.org> on 2023/11/13 17:40:00 UTC

[jira] [Updated] (SPARK-45892) Refactor the optimizer plan validation to decouple validateSchemaOutput and validateExprIdUniqueness

     [ https://issues.apache.org/jira/browse/SPARK-45892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xi Liang updated SPARK-45892:
-----------------------------
    Summary: Refactor the optimizer plan validation to decouple validateSchemaOutput and validateExprIdUniqueness  (was: Refactor the optimizer plan validation)

> Refactor the optimizer plan validation to decouple validateSchemaOutput and validateExprIdUniqueness
> ----------------------------------------------------------------------------------------------------
>
>                 Key: SPARK-45892
>                 URL: https://issues.apache.org/jira/browse/SPARK-45892
>             Project: Spark
>          Issue Type: Improvement
>          Components: Optimizer
>    Affects Versions: 3.4.0, 3.4.1
>            Reporter: Xi Liang
>            Priority: Major
>              Labels: pull-request-available
>
> Currently, the expressionIDUniqueness validation is closely coupled with output schema validation. 
> https://github.com/apache/spark/blob/master/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/LogicalPlan.scala#L403C7-L411C8
> Some refactoring can improve readability and reuse.



--
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