Added support for RECORD field type in schema definition #10
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
|
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed (or fixed any issues), please reply here (e.g. What to do if you already signed the CLAIndividual signers
Corporate signers
|
Author
|
Hi guys, I have added support for the nested RECORD type in a Big Query Schema to the TextIOToBigQuery template referenced in this issue: |
1 similar comment
Author
|
Hi guys, I have added support for the nested RECORD type in a Big Query Schema to the TextIOToBigQuery template referenced in this issue: |
Author
shreyakhajanchi
pushed a commit
that referenced
this pull request
Dec 17, 2024
* Type handler (#10) * Added Type Handler for Cassandra * Added UT * PR review comments fixes (#13) * Refectored the code * Handle Minor fixes * Casting fixes PR review comments fixed * Type handler review cm (#14) * updated comments * Add additional missing case as well (#16) * Resolve review comments and added test cases for null, min, max and incorrect value format * Handle Exception * Handle INet * Handle Code Formate * Added format and removeed raw import * Added Null handling * Added test cases for all remaining of cassandra datatype * Address the formatter case * Updated Comment * mvn spotless:apply fixes * Type handler ut fixes (#17) * removed unwanted <> from comments * Added Fixes for String formate * Fix spotapply * Type handler ut fixes (#18) * removed unwanted <> from comments * Added Fixes for String formate * Fix spotapply * Fixed the review comments and add Test with a non-zero offset and happy test * Fixed the review comments and add Test with a non-zero offset and happy test * Handle Sppoty fixes --------- Co-authored-by: Narendra Rajput <narendra.rajput@ollion.com> * Handle Inet from GCP package and also added Long Cast for List of Long * Fix UT and Checklist style * Handle Timestamp to Instant * Fix UT and consolidate Instant Parsing * Handle Fix related 2 date conversion * improved date parsing * Fixed review comments and coverage (#23) * Fixed review comments and increased coverage * ut_coverage_fixes * Fixed UT for Inetaddress --------- Co-authored-by: taherkl <taher.lakdawala@ollion.com> Co-authored-by: pawankashyapollion <v-pawan.kumar@ollion.com> Co-authored-by: Narendra Rajput <narendra.rajput@ollion.com>
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.
Hi guys,
I have added support for the nested RECORD type in a Big Query Schema to the TextIOToBigQuery template referenced in this issue:
#8