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

Posted to issues@spark.apache.org by "Santiago M. Mola (JIRA)" <ji...@apache.org> on 2015/07/06 09:29:04 UTC

[jira] [Commented] (SPARK-6981) [SQL] SparkPlanner and QueryExecution should be factored out from SQLContext

    [ https://issues.apache.org/jira/browse/SPARK-6981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14614645#comment-14614645 ] 

Santiago M. Mola commented on SPARK-6981:
-----------------------------------------

Any progress on this?

> [SQL] SparkPlanner and QueryExecution should be factored out from SQLContext
> ----------------------------------------------------------------------------
>
>                 Key: SPARK-6981
>                 URL: https://issues.apache.org/jira/browse/SPARK-6981
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 1.3.0, 1.4.0
>            Reporter: Edoardo Vacchi
>            Priority: Minor
>
> In order to simplify extensibility with new strategies from third-parties, it should be better to factor SparkPlanner and QueryExecution in their own classes. Dependent types add additional, unnecessary complexity; besides, HiveContext would benefit from this change as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org