[
https://issues.apache.org/jira/browse/SPARK-9662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14682267#comment-14682267
]
Joseph K. Bradley commented on SPARK-9662:
------------------------------------------
[~yanboliang] Thanks for checking for missing items! What is the status of
checking for Scala-Python inconsistency and Python API breaking changes?
Also, in the past, we have checked for inconsistency and API breaks manually,
just looking at the doc and code. If you have ideas for better solutions,
please say! I know it's a lot of work. Thanks again.
> ML 1.5 QA: API: Python API coverage
> -----------------------------------
>
> Key: SPARK-9662
> URL: https://issues.apache.org/jira/browse/SPARK-9662
> Project: Spark
> Issue Type: Sub-task
> Components: Documentation, ML, MLlib, PySpark
> Reporter: Joseph K. Bradley
> Assignee: Yanbo Liang
>
> 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) for this list of to-do items.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
