You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Xiangrui Meng (JIRA)" <ji...@apache.org> on 2015/05/19 08:15:00 UTC
[jira] [Commented] (SPARK-7458) Check 1.3-> 1.4 MLlib API
compliance using java-compliance-checker
[ https://issues.apache.org/jira/browse/SPARK-7458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14549861#comment-14549861 ]
Xiangrui Meng commented on SPARK-7458:
--------------------------------------
[~josephkb] The following changes would break binary compatibility. It should be fine since all of them are developer APIs, but we should mention the changes in the migration guide.
1. org.apache.spark.mllib.tree.loss.Loss.gradient
2. org.apache.spark.mllib.tree.configuration.BoostingStrategy.apply and copy (generated by case class). Adding/removing a field to/from a case class breaks binary compatibility.
3. org.apache.spark.mllib.clustering.LDA.run
> Check 1.3-> 1.4 MLlib API compliance using java-compliance-checker
> ------------------------------------------------------------------
>
> Key: SPARK-7458
> URL: https://issues.apache.org/jira/browse/SPARK-7458
> Project: Spark
> Issue Type: Sub-task
> Components: ML, MLlib
> Affects Versions: 1.4.0
> Reporter: Xiangrui Meng
> Assignee: Xiangrui Meng
> Attachments: compat_report.html
>
>
> We should do this after 1.4-rc1 is cut.
--
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