[
https://issues.apache.org/jira/browse/SPARK-9662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14693641#comment-14693641
]
Yanbo Liang commented on SPARK-9662:
------------------------------------
[~josephkb] Checking for inconsistency and breaking changes are almost
finished, I will submit the PR ASAP.
Yes, we need to find better solutions to do the check. I think we can build a
tool to help us finish the check process just like audit Python API. I think we
can finish it when 1.6 release.
If no anyone else work on a similar tool, I will try to build one. But some
implementation detail should be discussed, I can open another JIRA focus on it.
> 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
