spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "holdenk (JIRA)" <>
Subject [jira] [Commented] (SPARK-14813) ML 2.0 QA: API: Python API coverage
Date Fri, 06 May 2016 20:54:12 GMT


holdenk commented on SPARK-14813:

[~yanboliang]Just following up since I've done a first pass through classifcation and eveluator
- are you working on regression?

> ML 2.0 QA: API: Python API coverage
> -----------------------------------
>                 Key: SPARK-14813
>                 URL:
>             Project: Spark
>          Issue Type: Sub-task
>          Components: Documentation, ML, PySpark
>            Reporter: Joseph K. Bradley
>            Assignee: holdenk
> 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.
> UPDATE: This only needs to cover since spark.mllib is going into maintenance

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message