[WIP] Partition-metadata tracking in Dask-DataFrame #3
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.
Brief proposal for a performance-motivated metadata update in Dask-DataFrame.
NOTE: Although this proposal is distinct from a high-level graph or query-optimization system, it should make such a system much easier to implement! I say this, because we will still want to be tracking and managing the same kind of metadata in one place.
See also: dask/dask#9473