Keep legacy proto-based types available for import #999
Labels
api: bigquery
Issues related to the googleapis/python-bigquery API.
semver: major
Hint for users that this is an API breaking change.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
As a follow-up to #814 and as discussed with @tswast on the chat, some users, that otherwise could upgrade to a
3.x
version, would still need the legacy generated SQL model types that the3.x
version will remove.We should add these models back to the codebase, but with the following restrictions:
main
should be the time [Breaking Change] Removegoogle.cloud.bigquery_v2
directory and related code generation #814 was merged intov3
.@tswast Feel free to update/correct the requirements above in case I misunderstood/misremembered them.
The text was updated successfully, but these errors were encountered: