Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/19876
@MLnick I think the read path could follow a similar approach, but for
models which we export from Spark and wish to load back into Spark the internal
format is probably the best option.
As far as options, this keeps the same stringly typed options interface as
we have with Datasources, and individual writers are free to specialize and add
their own special methods.
I'm open to the idea of punting this, but we've punted PMML export since we
introduced ML pipelines and users are still asking for general export support
so the feature req hasn't gone away either. If we think the design needs
another pass that's fine, but I'd like to suggest that this is probably a good
starting block from which we can add more things on top off.
If folks agree the foundation isn't bad I think putting it in for 2.3 would
be useful (and it's not like we haven't had a long time to consider this
design). This specific PR has been open since Dec 4th but we've been looking at
variants on this idea for years.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
