GitHub user rxin opened a pull request:

    Graduate a list of Spark SQL APIs to stable

    ## What changes were proposed in this pull request?
    This patch graduates a list of Spark SQL APIs and mark them stable.
    The following are marked stable:
    - functions, since 1.3
    - ColumnName, since 1.3
    - DataFrameNaFunctions, since 1.3.1
    - DataFrameStatFunctions, since 1.4
    - UserDefinedFunction, since 1.3
    - UserDefinedAggregateFunction, since 1.5
    - Window and WindowSpec, since 1.4
    Data sources:
    - DataSourceRegister, since 1.5
    - RelationProvider, since 1.3
    - SchemaRelationProvider, since 1.3
    - CreatableRelationProvider, since 1.3
    - BaseRelation, since 1.3
    - TableScan, since 1.3
    - PrunedScan, since 1.3
    - PrunedFilteredScan, since 1.3
    - InsertableRelation, since 1.3
    The following are kept experimental / evolving:
    Data sources:
    - CatalystScan (tied to internal logical plans so it is not stable by 
    Structured streaming:
    - all classes (introduced new in 2.0 and will likely change)
    Dataset typed operations (introduced in 1.6 and 2.0 and might change, 
although probability is low)
    - all typed methods on Dataset
    - KeyValueGroupedDataset
    - o.a.s.sql.expressions.javalang.typed
    - o.a.s.sql.expressions.scalalang.typed
    - methods that return typed Dataset in SparkSession
    We should discuss more whether we want to mark Dataset typed operations 
stable in 2.1.
    ## How was this patch tested?
    N/A - just annotation changes.

You can merge this pull request into a Git repository by running:

    $ git pull SPARK-17900

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #15469
commit 2b15329ac06bcbd808c15ec735fab7dd7415bfb6
Author: Reynold Xin <>
Date:   2016-10-13T20:29:16Z

    Graduate a list of Spark SQL APIs to stable


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to