[ https://issues.apache.org/jira/browse/SPARK-6981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14552223#comment-14552223 ]
Edoardo Vacchi commented on SPARK-6981: --------------------------------------- Besides, is there any particular reason why both these classes are {{protected[sql]}} ? > [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-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org