You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Reynold Xin (JIRA)" <ji...@apache.org> on 2016/11/01 21:18:58 UTC
[jira] [Updated] (SPARK-16576) Move plan SQL generation code from
SQLBuilder into logical operators
[ https://issues.apache.org/jira/browse/SPARK-16576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Reynold Xin updated SPARK-16576:
--------------------------------
Target Version/s: 2.2.0 (was: 2.1.0)
> 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
> 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-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org