[
https://issues.apache.org/jira/browse/SPARK-16576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reynold Xin closed SPARK-16576.
-------------------------------
Resolution: Won't Fix
I'm marking this as won't fix since we can do it better using the approach
outlined here: SPARK-18209
> Move plan SQL generation code from SQLBuilder into logical operators
> --------------------------------------------------------------------
>
> Key: SPARK-16576
> URL: https://issues.apache.org/jira/browse/SPARK-16576
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 2.0.1
> Reporter: Reynold Xin
>
> We currently handle all SQL query generation in a single class (SQLBuilder).
> This has many disadvantages:
> 1. It is not extensible, i.e. it is not possible to introduce a new logical
> operator, even just for experimentation purpose, without modifying Spark.
> 2. It is very fragile. When we introduce a new logical operator, it is very
> likely that we forget to update SQLBuilder and then the use of that new
> logical operator would fail view definition.
> We should move the SQL definition part into logical operators themselves, so
> this becomes more robust and scalable.
--
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
