[
https://issues.apache.org/jira/browse/SPARK-21619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113526#comment-16113526
]
Mark Hamstra commented on SPARK-21619:
--------------------------------------
Two reason, mostly: 1) To provide better guarantees that plans that are deemed
to be semantically equivalent actually end up being expressed the same way
before execution and thus go down the same code paths; 2) To simplify some
downstream logic; so instead of needing to maintain a mapping between multiple,
semantically equivalent plans and a single canonical form, after a certain
canonicalization point the plans really are the same.
To perhaps clear up my confusion, maybe you can answer the question going the
other way: Why would you want to execute multiple semantically equivalent plans
in different forms?
> Fail the execution of canonicalized plans explicitly
> ----------------------------------------------------
>
> Key: SPARK-21619
> URL: https://issues.apache.org/jira/browse/SPARK-21619
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 2.2.0
> Reporter: Reynold Xin
> Assignee: Reynold Xin
>
> Canonicalized plans are not supposed to be executed. I ran into a case in
> which there's some code that accidentally calls execute on a canonicalized
> plan. This patch throws a more explicit exception when that happens.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
