[Data] Make Parquet tests more robust and expose Parquet logic #46944
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.
Why are these changes needed?
This PR makes the following changes:
test_dataset_stats_read_parquet
astest_dataset_stats_range
to make the test independent of the Parquet implementation (the intent of the test isn't Parquet-specific)test_parquet_read_spread
robust to different Parquet implementations (the test makes assumptions about how tasks are launched)test_fsspec_filesystem
not depend on the number of files written by Ray Data (the test assumeswrite_parquet
writes exactly two files)SerializedFragment
andcheck_for_legacy_tensor_type
ParquetDatasource._sample_fragments
assample_fragments
get_parquet_dataset
Related issue number
Checks
git commit -s
) in this PR.scripts/format.sh
to lint the changes in this PR.method in Tune, I've added it in
doc/source/tune/api/
under thecorresponding
.rst
file.