In ARROW-3861 (#7050), I "fixed" a bug that the partition columns are always included even when the user did a manual column selection.
But apparently, this behaviour was being relied upon by dask. See the failing nightly integration tests: https://circleci.com/gh/ursa-labs/crossbow/11854?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link
So the best option might be to just keep the "old" behaviour for the legacy ParquetDataset, when using the new datasets API (use_legacy_datasets=False), you get the new / correct behaviour.
Reporter: Joris Van den Bossche / @jorisvandenbossche
Assignee: Joris Van den Bossche / @jorisvandenbossche
PRs and other links:
Note: This issue was originally created as ARROW-8644. Please see the migration documentation for further details.
In ARROW-3861 (#7050), I "fixed" a bug that the partition columns are always included even when the user did a manual column selection.
But apparently, this behaviour was being relied upon by dask. See the failing nightly integration tests: https://circleci.com/gh/ursa-labs/crossbow/11854?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link
So the best option might be to just keep the "old" behaviour for the legacy ParquetDataset, when using the new datasets API (
use_legacy_datasets=False), you get the new / correct behaviour.Reporter: Joris Van den Bossche / @jorisvandenbossche
Assignee: Joris Van den Bossche / @jorisvandenbossche
PRs and other links:
Note: This issue was originally created as ARROW-8644. Please see the migration documentation for further details.