spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Owen (JIRA)" <>
Subject [jira] [Commented] (SPARK-17436) dataframe.write sometimes does not keep sorting
Date Thu, 27 Oct 2016 10:26:58 GMT


Sean Owen commented on SPARK-17436:

Yes, but a partitioning operation does not necessarily preserve ordering. Of course you can
order it after that . Can you provide a pull request to show what you mean?

> dataframe.write sometimes does not keep sorting
> -----------------------------------------------
>                 Key: SPARK-17436
>                 URL:
>             Project: Spark
>          Issue Type: Bug
>    Affects Versions: 1.6.1, 1.6.2, 2.0.0
>            Reporter: Ran Haim
> When using partition by,  datawriter can sometimes mess up an ordered dataframe.
> The problem originates in org.apache.spark.sql.execution.datasources.DynamicPartitionWriterContainer.
> In the writeRows method when too many files are opened (configurable), it starts inserting
rows to UnsafeKVExternalSorter, then it reads all the rows again from the sorter and writes
them to the corresponding files.
> The problem is that the sorter actually sorts the rows using the partition key, and that
can sometimes mess up the original sort (or secondary sort if you will).
> I think the best way to fix it is to stop using a sorter, and just put the rows in a
map using key as partition key and value as an arraylist, and then just walk through all the
keys and write it in the original order - this will probably be faster as there no need for

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message