Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/12836#issuecomment-221142351
@NarineK @sun-rui Thanks a lot for your work on this PR.
I think the second option (of giving key and data.frame) is more intuitive
/ flexible as well. Would be good to investigate if that matches the
`aggregate` use case that @thunterdb brings up.
BTW I also think that at the underlying implementation level we should
support the most general form and then we can have higher level APIs that
ignore the key etc.
Also @davies would be great if you could take a look at this updated
version.
---
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]
