[
https://issues.apache.org/jira/browse/SPARK-21619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113536#comment-16113536
]
Reynold Xin commented on SPARK-21619:
-------------------------------------
Mark that's a great point but you are going into the existential question of
how we should design query execution and potentially overthrow the entire
architecture here. The way canonicalization is defined as is in Spark is that
it is not meant for execution. This ticket simply enforces that with a few line
of change.
If we want to redesign how query execution should work (I don't see why we
would want to since I don't see much real practical benefits given we already
have sameResult and semanticHash), we should do it separately.
"Why would you want to execute multiple semantically equivalent plans in
different forms?" -> Because they can be executed in different times, using
different aliases, etc?
> 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
