Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/2083#issuecomment-53367217
Actually I commented on the JIRA -- I'm not sure this is a bug. distinct()
makes no guarantees on the order of results obtained, and in general, our
shuffle operations shouldn't make guarantees about a specific order (unless you
are explicitly calling sortByKey). So unless values are missing from the
resulting set somehow, I wouldn't consider this a bug. Your code can always
call sortByKey or call mapPartitions to sort within a partition if you want a
specific order.
---
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]
