Specify to_parquet keys explicitly to ensure ordering #3270
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously we used delayed functions here, which don't order things in
an obvious way. Our task ordering heuristics use keys as tie-breakers
so they were performing sub-optimally when writing parquet data to disk
In the future, when convenient, we should endeavor to make our keys look
like the following:
flake8 dask
docs/source/changelog.rst
for all changesand one of the
docs/source/*-api.rst
files for new API