fix: populate destinationTable for queries without explicit destination #425
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
Fixes goccy#183 where destinationTable field wasn't being returned when queries run without explicit destination tables. This affects Ruby, Java, Scala, and Go BigQuery clients. Changes: - Add 'ds_' prefix to dataset ID to avoid conflicts when dataset and table names are the same - Populate job.Configuration.Query.DestinationTable with proper references Co-authored-by: Josef Šimánek <[email protected]> (added tests)
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.
building on top of #187 with added tests
Fixes #183 #180 #187 where destinationTable field wasn't being returned when queries run without explicit destination tables. This affects Ruby, Java, Scala, and Go BigQuery clients.
Changes:
(added tests)