Github user selvinsource commented on the pull request:
https://github.com/apache/spark/pull/3062#issuecomment-61812768
@srowen
For the fields I have the same opinion, the exporter shouldn't ask the user
to provide the fields name, the model should be aware of that and I am glad
this is upcoming.
It would be great if it is committed at least internally and, I assume, it
can be used from the spark-shell. There are scenarios whereas it useful, for
exampe: load the exported pmml file in JPMML Evaluator and use it to do the
prediction without the need of tying the app to Spark.
I attached to Jira the updated version of the PDF and the PMML xml
generated by the ModelExporter object. For reference I attached my test class
that proved JPMML Evaluator gives the same result of KMeansModel.predict.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
