[
https://issues.apache.org/jira/browse/SPARK-11988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15030456#comment-15030456
]
Sean Owen commented on SPARK-11988:
-----------------------------------
[~selvinsource] I changed the PR to use the PMML constructor that takes a
version.
[~vfed] yes that's actually a reason I want to update, to avoid conflicts for
the exact same reason. It's not a solution like shading is, but happens to
solve the problem while getting some bug fixes in, while minimizes
compatibility issues (i.e. shading means the dependency disappears from Spark
apps, which it kind of should have done already). I assume 1.2.x might be more
stable API-wise.
> Update JPMML to 1.2.7
> ---------------------
>
> Key: SPARK-11988
> URL: https://issues.apache.org/jira/browse/SPARK-11988
> Project: Spark
> Issue Type: Improvement
> Components: ML, MLlib
> Affects Versions: 1.5.2
> Reporter: Sean Owen
> Assignee: Sean Owen
> Priority: Minor
>
> Pretty much says it all: update to the more recent JPMML 1.2.x line from
> 1.1.x.
> The API did change between the 2 versions, though all use of it is internal
> to Spark, so doesn't affect end users in theory.
> In practice, JPMML leaks into the classpath and might cause issues. My
> rationale for the change is that 1.2.x is more recent and more stable (right
> [~vfed]?) so if people are going to run into it, might as well run into
> something more modern.
> And bug fixes and more support and all that.
> CC [~selvinsource]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
