Fix the bug introduced by this commit 350d5443a19e0c8db8aec0eae74624e2235c7d3f #20871
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
|
/test connector=connectors/destination-bigquery-denormalized
Build FailedTest summary info: |
grishick
temporarily deployed
to
more-secrets
GitHub Actions
Inactive
|
Closing in favor of #20640 |
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.
Destination BigQuery denormalized does not support normalization. The change that added normalization definitions to actor definitions table (350d544) broke DATs for bigquery denormalized by erroneously adding normalization config for it. This change removes normalization config from
destination-bigquery-denormalizedindestination_definitions.yaml