spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joseph K. Bradley (JIRA)" <>
Subject [jira] [Updated] (SPARK-16486) Python API parity issues from 2.0 QA
Date Mon, 11 Jul 2016 21:04:11 GMT


Joseph K. Bradley updated SPARK-16486:
    Issue Type: Umbrella  (was: Sub-task)
        Parent:     (was: SPARK-14808)

> Python API parity issues from 2.0 QA
> ------------------------------------
>                 Key: SPARK-16486
>                 URL:
>             Project: Spark
>          Issue Type: Umbrella
>          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 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