Drop JSON null values on streams #428
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
|
Hello @mariuene @TSommerdal, do you think it would be possible to review / merge / release this? Many thanks! |
TSommerdal
reviewed
Jan 8, 2025
|
(Wonderful! Do you have plans for a release?) edit: wow already released, thanks! |
|
👍 |
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.
When sending data with
loadJson, emptyOptionproperties are sent as JSONnull. While BigQuery then stores it as a columnnullfor almost all column types, it is not the case with JSON column types.For example:
None=> stored as JSONnull(not columnnull)Some(null)The change is simple: just remove the
nullJSON properties so that BigQuery always stores a DBnull, even with the JSON column type.