You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Joseph K. Bradley (JIRA)" <ji...@apache.org> on 2016/07/19 20:26:21 UTC
[jira] [Resolved] (SPARK-14817) ML, Graph, R 2.0 QA: Programming
guide update and migration guide
[ https://issues.apache.org/jira/browse/SPARK-14817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joseph K. Bradley resolved SPARK-14817.
---------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
Closing...
> ML, Graph, R 2.0 QA: Programming guide update and migration guide
> -----------------------------------------------------------------
>
> Key: SPARK-14817
> URL: https://issues.apache.org/jira/browse/SPARK-14817
> Project: Spark
> Issue Type: Sub-task
> Components: Documentation, GraphX, ML, MLlib, SparkR
> Reporter: Joseph K. Bradley
> Assignee: Joseph K. Bradley
> Priority: Critical
> Fix For: 2.0.0
>
>
> Before the release, we need to update the MLlib, GraphX, and SparkR Programming Guides. Updates will include:
> * Add migration guide subsection.
> ** Use the results of the QA audit JIRAs and [SPARK-13448].
> * Check phrasing, especially in main sections (for outdated items such as "In this release, ...")
> For MLlib, we will make the DataFrame-based API (spark.ml) front-and-center, to make it clear the RDD-based API is the older, maintenance-mode one.
> * No docs for spark.mllib will be deleted; they will just be reorganized and put in a subsection.
> * If spark.ml docs are less complete, or if spark.ml docs say "refer to the spark.mllib docs for details," then we should copy those details to the spark.ml docs. This per-feature work can happen under [SPARK-14815].
> * This big reorganization should be done *after* docs are added for each feature (to minimize merge conflicts).
--
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