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/11 21:04:11 UTC
[jira] [Created] (SPARK-16486) Python API parity issues from 2.0 QA
Joseph K. Bradley created SPARK-16486:
-----------------------------------------
Summary: Python API parity issues from 2.0 QA
Key: SPARK-16486
URL: https://issues.apache.org/jira/browse/SPARK-16486
Project: Spark
Issue Type: Sub-task
Components: Documentation, ML, PySpark
Reporter: Joseph K. Bradley
Assignee: holdenk
Priority: Blocker
For new public APIs added to MLlib, we need to check the generated HTML doc and compare the Scala & Python versions. We need to track:
* Inconsistency: Do class/method/parameter names match?
* Docs: Is the Python doc missing or just a stub? We want the Python doc to be as complete as the Scala doc.
* API breaking changes: These should be very rare but are occasionally either necessary (intentional) or accidental. These must be recorded and added in the Migration Guide for this release.
** Note: If the API change is for an Alpha/Experimental/DeveloperApi component, please note that as well.
* Missing classes/methods/parameters: We should create to-do JIRAs for functionality missing from Python, to be added in the next release cycle. Please use a *separate* JIRA (linked below as "requires") for this list of to-do items.
** *NOTE: These missing features should be added in the next release. This work is just to generate a list of to-do items for the future.*
UPDATE: This only needs to cover spark.ml since spark.mllib is going into maintenance mode.
--
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