[
https://issues.apache.org/jira/browse/SPARK-11988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15029319#comment-15029319
]
Villu Ruusmann commented on SPARK-11988:
----------------------------------------
PMML@version is a required attribute. Your IDE should bring it to your
attention everytime you instantiate a new org.dmg.pmml.PMML object - always
choose an overloaded constructor over the default (ie. no-arg) constructor.
I would recommend you to set up some utility class that takes care of
initializing basic document structure. For example, I have a general purpose
JPMML-Converter project that I include to specialized JPMML-R and JPMML-SkLearn
converter projects.
> 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
