Add support for VARBYTE type#171
Open
aajisaka wants to merge 1 commit into
Open
Conversation
Author
|
@bsharifi Would you review? |
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
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.
Problem
Fails to read from Redshift table if the table has VARBYTE type column
Testing
Built from source, add the jar in Glue 5.0, and ran a Spark job to write binary data to Redshift table and read them from the same table.
I didn't update the unit tests, but I'm willing to work on that. Please let me know how I can efficiently implement unit tests for the new type.
Notes
tempformattoPARQUETinstead ofAVRO(default). Otherwise it fails with "The hex string size for Varbyte must be an even number" error. It seems Redshift LOAD from Avro doesn't support binary type.