Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/3062#issuecomment-61793044
Yes looking nice. @mengxr what do you think about `private[mllib]`? keep it
internal for now? if it's exposed, I think some of the traits may have to
change for Java interoperability.
My big question now is just whether this helps much if you can't identify
the fields!
You could ask users to pass in the names of the fields, although that feels
a bit ugly.
It feels like something that could get schema info from the upcoming
Dataset API changes. Maybe it can wait until then, or if it's committed, stay
internal-only for the moment?
---
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]
