You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2015/12/01 11:32:10 UTC

[jira] [Updated] (SPARK-11988) Update JPMML to 1.2.7

     [ https://issues.apache.org/jira/browse/SPARK-11988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Owen updated SPARK-11988:
------------------------------
    Target Version/s: 1.7.0

[~mengxr] the only real problem in play here is that JPMML 1.1 and 1.2 are a little bit mutually incompatible, so shading is needed in the user app or in Spark if different versions are used. Really, we could fix that by shading, but this was a gentler step to at least make the default the newer 1.2 version that people are likely to use. Still, that does change compatibility with apps using 1.1 I suppose so let's keep this for 1.7+ only.

The dependency graph is slightly improved in 1.2 since JAXB won't come in by default:

{code}
[INFO] +- org.jpmml:pmml-model:jar:1.1.15:compile
[INFO] |  +- org.jpmml:pmml-agent:jar:1.1.15:compile
[INFO] |  +- org.jpmml:pmml-schema:jar:1.1.15:compile
[INFO] |  \- com.sun.xml.bind:jaxb-impl:jar:2.2.7:compile
[INFO] |     \- com.sun.xml.bind:jaxb-core:jar:2.2.7:compile
[INFO] |        \- javax.xml.bind:jaxb-api:jar:2.2.7:compile
{code}

{code}
[INFO] +- org.jpmml:pmml-model:jar:1.2.7:compile
[INFO] |  +- org.jpmml:pmml-agent:jar:1.2.7:compile
[INFO] |  \- org.jpmml:pmml-schema:jar:1.2.7:compile
{code}

> 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-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org