Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ARROW-3861: [Python] ParquetDataset.read() respect specified columns and not include partition columns #7050

Conversation

jorisvandenbossche
Copy link
Member

@jorisvandenbossche jorisvandenbossche commented Apr 28, 2020

This is adding a test for it (using both legacy and new dataset), and also small fix for the legacy path.

@github-actions
Copy link

@jorisvandenbossche jorisvandenbossche deleted the ARROW-3861-parquet-dataset-read-columns branch April 29, 2020 06:21
@jorisvandenbossche
Copy link
Member Author

Hmm, I should have thought about triggering the dask integration tests for this ... -> https://issues.apache.org/jira/browse/ARROW-8644

wesm pushed a commit that referenced this pull request May 5, 2020
…de partition column for dask compatibility

Given that the original change (https://issues.apache.org/jira/browse/ARROW-3861 / #7050) breaks dask's reading of partitioned datasets (it doesn't add the partition column to the list of columns to read, but expects it will still be read automatically), it doesn't seem worth it to me to fix this in the "old" ParquetDataset implementation.

But we can keep the "correct" behaviour in the Datasets API - based implementation going forward.

Closes #7096 from jorisvandenbossche/ARROW-8644-dask-partitioned

Authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>
Signed-off-by: Wes McKinney <wesm+git@apache.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants