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/07/06 06:12:11 UTC

[jira] [Issue Comment Deleted] (SPARK-13485) (Dataset-oriented) API evolution in Spark 2.0

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

Reynold Xin updated SPARK-13485:
--------------------------------
    Comment: was deleted

(was: User 'dilipbiswal' has created a pull request for this issue:
https://github.com/apache/spark/pull/13102)

> (Dataset-oriented) API evolution in Spark 2.0
> ---------------------------------------------
>
>                 Key: SPARK-13485
>                 URL: https://issues.apache.org/jira/browse/SPARK-13485
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Reynold Xin
>            Assignee: Reynold Xin
>            Priority: Blocker
>              Labels: releasenotes
>             Fix For: 2.0.0
>
>         Attachments: API Evolution in Spark 2.0.pdf
>
>
> As part of Spark 2.0, we want to create a stable API foundation for Dataset to become the main user-facing API in Spark. This ticket tracks various tasks related to that.
> The main high level changes are:
> 1. Merge Dataset/DataFrame
> 2. Create a more natural entry point for Dataset (SQLContext/HiveContext are not ideal because of the name "SQL"/"Hive", and "SparkContext" is not ideal because of its heavy dependency on RDDs)
> 3. First class support for sessions
> 4. First class support for some system catalog
> See the design doc for more details.



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