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/01/18 07:17:39 UTC

[jira] [Updated] (SPARK-12855) Remove parser pluggability

     [ https://issues.apache.org/jira/browse/SPARK-12855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Reynold Xin updated SPARK-12855:
--------------------------------
    Description: 
This pull request removes the public developer parser API for external parsers. Given everything a parser depends on (e.g. logical plans and expressions) are internal and not stable, external parsers will break with every release of Spark. It is a bad idea to create the illusion that Spark actually supports pluggable parsers. In addition, this also reduces incentives for 3rd party projects to contribute parse improvements back to Spark.

The number of applications that are using this feature is small (as far as I know it came down from two to one as of Jan 2016, and will be 0 once we have better ansi SQL support).


  was:
The number of applications that are using this feature is small (as far as I know it came down from two to one as of Jan 2016). No other database systems support this feature, and it actually encourages 3rd party projects to not contribute their improvements back to Spark. We should just remove this functionality to simplify our own code base.



> Remove parser pluggability
> --------------------------
>
>                 Key: SPARK-12855
>                 URL: https://issues.apache.org/jira/browse/SPARK-12855
>             Project: Spark
>          Issue Type: Sub-task
>          Components: SQL
>            Reporter: Reynold Xin
>            Assignee: Reynold Xin
>
> This pull request removes the public developer parser API for external parsers. Given everything a parser depends on (e.g. logical plans and expressions) are internal and not stable, external parsers will break with every release of Spark. It is a bad idea to create the illusion that Spark actually supports pluggable parsers. In addition, this also reduces incentives for 3rd party projects to contribute parse improvements back to Spark.
> The number of applications that are using this feature is small (as far as I know it came down from two to one as of Jan 2016, and will be 0 once we have better ansi SQL support).



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