Skip to content

v3: add migration helpers and guide for breaking changes #960

@tswast

Description

@tswast

I'd like to make sure we don't get folks stuck on v2. I know we have some internal (Google) customers who rely on the BQML stats protobuf messages (the ones in google.cloud.bigquery_v2.

I propose

  1. We restore the files in google.cloud.bigquery_v2, but document that they are deprecated and are not updated.
  2. We continue to return dictionaries in the relevant classes, so that all stays the same.
  3. We document in the UPGRADING guide how to manually convert from the dictionaries to the classes in google.cloud.bigquery_v2 with some code samples.

Regarding the pandas connector changes, we should also document those in the UPGRADING guide, ideally with code samples on how to get / convert to the old dtypes if desired.

Metadata

Metadata

Assignees

No one assigned

    Labels

    api: bigqueryIssues related to the googleapis/python-bigquery API.next major: breaking changethis is a change that we should wait to bundle into the next major versionsemver: majorHint for users that this is an API breaking change.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions