René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[Breaking Change] Remove `google.cloud.bigquery_v2` directory and related code generation","articleBody":"The `google.cloud.bigquery_v2` modules are frequently out-of-date. This primarily affect the usability of BigQuery ML.\r\n\r\nSince BigQuery is a REST API, protobuf changes must be synced manually in internal code repo before they can be published to https://github.com/googleapis/googleapis\r\n\r\nIn the years since we first introduced `google.cloud.bigquery_v2`, we've seen that BigQuery ML adds model stats and model types much more frequently than the protobuf changes are actually published.\r\n\r\nWe've worked around this by:\r\n\r\n* I and @shollyman (mostly @shollyman lately) republish the protos when a customer has a problem, such as in https://github.com/googleapis/python-bigquery/issues/293\r\n* Avoiding the worst exceptions when an enum or property isn't present, such as in https://github.com/googleapis/python-bigquery/issues/334\r\n\r\n**Solution**\r\n\r\n* [x] Remove `google.cloud.bigquery_v2` modules\r\n* [x] Update owlbot config to stop generating \"client\"\r\n* [x] In the BigQuery ML classes, whereever we were returning protobuf object, return the JSON-parsed API response, instead.\r\n  * [x] Complex types become dictionaries.\r\n  * [x] Enums become strings.\r\n* [x] In the routines logic, create manual wrappers and enums where needed.\r\n\r\nSupersedes https://github.com/googleapis/python-bigquery/issues/319","author":{"url":"https://github.com/tswast","@type":"Person","name":"tswast"},"datePublished":"2021-07-26T21:26:21.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/814/python-bigquery/issues/814"}