Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16724
I think it's hard to reason about how/when to preserve the data ordering
when writing, considering partitioning and bucketing. For now it looks like the
ordering **should** be preserved if the writer doesn't specify partitioning and
bucketing, or the specified partitioning is same as the input data.
If we implement the optimization mentioned above, then we can preserve the
ordering if the specified partitioning is same as the input data.
---
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]
