Guard our BigQuery release metadata sync against upcoming schema changes #16956
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.
PEP 639 implementation will need the following columns added to the big query schema:
license_expression, STRING, NULLABLE
license_files, STRING, REPEATED
We'll want that done in advance of merging an implementation, but need to have the Big Query public dataset team do that for us... so to avoid the need for coordination, lets guard ourselves against the schema changing underneath us...