You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Yanbo Liang (JIRA)" <ji...@apache.org> on 2015/08/09 06:17:45 UTC

[jira] [Commented] (SPARK-9662) ML 1.5 QA: API: Python API coverage

    [ https://issues.apache.org/jira/browse/SPARK-9662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14663255#comment-14663255 ] 

Yanbo Liang commented on SPARK-9662:
------------------------------------

I have list missing classes/methods/parameters at SPARK-9663

> 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-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org