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

Joseph K. Bradley edited comment on SPARK-7529 at 5/28/15 3:50 AM:
-------------------------------------------------------------------

I've finished a pass.  I mainly checked for "Object" in the Java docs.  I tried 
to look out for other issues (important missing doc, Scala enums, Scala objects 
causing MODULE$ notation), but I was not that careful about it since we have 
not added many items which could be problematic.

I added some tags above for "*TARGET 1.4*" for the more critical items.


was (Author: josephkb):
I've finished a pass.  I mainly checked for "Object" in the Java docs.  I tried 
to look out for other issues (important missing doc, Scala enums, Scala objects 
causing MODULE$ notation), but I was not that careful about it since we have 
not added many items which could be problematic.

I added some tags above for *TARGET: 1.4* for the more critical items.

> Java compatibility check for MLlib 1.4
> --------------------------------------
>
>                 Key: SPARK-7529
>                 URL: https://issues.apache.org/jira/browse/SPARK-7529
>             Project: Spark
>          Issue Type: Sub-task
>          Components: ML, MLlib
>    Affects Versions: 1.4.0
>            Reporter: Xiangrui Meng
>            Assignee: Joseph K. Bradley
>
> Check Java compatibility for MLlib 1.4. We should create separate JIRAs for 
> each possible issue.
> Checking compatibility means:
> * comparing with the Scala doc
> * verifying that Java docs are not messed up by Scala type incompatibilities 
> (E.g., check for generic "Object" types where Java cannot understand complex 
> Scala types.  Also check Scala objects (especially with nesting!) carefully.
> * If needed for complex issues, create small Java unit tests which execute 
> each method.  (The correctness can be checked in Scala.)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to