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

2015-07-06 Thread Santiago M. Mola (JIRA) 

[ 
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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

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

2015-05-22 Thread Edoardo Vacchi (JIRA) 

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

Edoardo Vacchi commented on SPARK-6981:
---

pull #6356 is a lighter-weight alternative that should retain binary 
compatibility

> [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

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

2015-05-22 Thread Apache Spark (JIRA) 

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

Apache Spark commented on SPARK-6981:
-

User 'evacchi' has created a pull request for this issue:
https://github.com/apache/spark/pull/6356

> [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

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

2015-05-20 Thread Edoardo Vacchi (JIRA) 

[ 
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

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

2015-05-13 Thread Apache Spark (JIRA) 

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

Apache Spark commented on SPARK-6981:
-

User 'evacchi' has created a pull request for this issue:
https://github.com/apache/spark/pull/6122

> [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
> Fix For: 1.4.0
>
>
> 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

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

2015-04-17 Thread Apache Spark (JIRA) 

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

Apache Spark commented on SPARK-6981:
-

User 'evacchi' has created a pull request for this issue:
https://github.com/apache/spark/pull/5556

> [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
> Fix For: 1.4.0
>
>
> 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