Uh oh!
There was an error while loading. Please reload this page.
Avro Table Provider - #910
Merged
Merged
Conversation
Loading
Uh oh!
There was an error while loading. Please reload this page.
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
8 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.
Which issue does this PR close?
Closes#903.
Rationale for this change
Enables loading avro data files through datafusion.
What changes are included in this PR?
Avro is added as a table provider and a supported file format.
Avro schemas can be translated into arrow schemas.
Are there any user-facing changes?
Yes, as one can now call register_avro on df and 'STORED AS AVRO' in sqsl.
N.B.:
Missing :
I find there is duplication between modules with these additions, I should probably do some refactoring.