[SPARK-46746][SQL][AVRO] Attach codec extension to avro datasource files #44770
Conversation
This file contains hidden or 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
dongjoon-hyun
approved these changes
Jan 17, 2024
Member
dongjoon-hyun
left a comment
dongjoon-hyun
left a comment
There was a problem hiding this comment.
+1, LGTM. Ya, this looks consistent with other formats. Thank you, @yaooqinn .
Member
|
Merged to master for Apache Spark 4. |
Member
Author
|
Thank you very much @dongjoon-hyun |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What changes were proposed in this pull request?
This PR attaches codec extension to avro datasource files.
Why are the changes needed?
Feature parity with parquet and orc file sources, which is useful to differentiate compression codecs of Avro files
Does this PR introduce any user-facing change?
No, this more likely belong to underlying data storage layer
How was this patch tested?
new unit tests
Was this patch authored or co-authored using generative AI tooling?
no