spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Hamstra (JIRA)" <>
Subject [jira] [Commented] (SPARK-21619) Fail the execution of canonicalized plans explicitly
Date Thu, 03 Aug 2017 22:19:00 GMT


Mark Hamstra commented on SPARK-21619:

But part of the point of the split in my half-baked example is to fork the query execution
pipeline before physical plan generation, allowing the cost of that generation to be parallelized
with an instance per execution engine. Yes, maybe doing dispatch of physical plans via the
CBO or other means is all that I should realistically hope for, but it doesn't mean that it
isn't worth thinking about alternatives. 

> Fail the execution of canonicalized plans explicitly
> ----------------------------------------------------
>                 Key: SPARK-21619
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message