fix: avoid compressed json files repartitioning #10470
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alamb
approved these changes
May 13, 2024
| @@ -154,7 +154,7 @@ impl ExecutionPlan for NdJsonExec { | |||
| target_partitions: usize, | |||
| config: &datafusion_common::config::ConfigOptions, | |||
| ) -> Result<Option<Arc<dyn ExecutionPlan>>> { | |||
| if self.file_compression_type == FileCompressionType::GZIP { | |||
| if self.file_compression_type.is_compressed() { | |||
|
Thanks again @korowa |
findepi
pushed a commit
to findepi/datafusion
that referenced
this pull request
Jul 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Which issue does this PR close?
Closes #10435.
Rationale for this change
Turning off repartitioning for compressed JSON files allows not to fail on reading such files.
What changes are included in this PR?
Same as above
Are these changes tested?
Test for reading gzipped JSON with forced repartitioning (controlled by settings), extended with other compression types.
Are there any user-facing changes?
No