feat(bigquery): add support for bignumeric #2779
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
This is an in-progress change to support BIGNUMERIC values.
shollyman
added
the
do not merge
google-cla
bot
added
the
cla: yes
product-auto-label
bot
added
the
api: bigquery
tbpg
suggested changes
Nov 18, 2020
tbpg
approved these changes
Nov 19, 2020
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.
This PR adds basic support for the BIGNUMERIC type in BigQuery.
This library has several cases where it tries to infer the appropriate BigQuery type from a native Go type. For
big.Rattypes, we continue the existing behavior of mapping them to NUMERIC, as the big.Rat doesn'tprovide a general way of indicating desired precision or scale to determine whether BIGNUMERIC is a more
appropriate mapping.