-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
all: remove last uses of gtransport.Dial #1777
Comments
These will be handled by moving to microgenerator. |
This client should be removed, it doesn't conform to |
Any ETA on that, @noahdietz? Primarily concerned about |
The |
These aren't generated anymore and require manual work. I have little context on why they aren't generated anymore. |
Current list as of Feb 26, 2020: Moving to new generator soon:
Fixed soon due to migration to microgenerator:
Stale/not generated anymore (per comment above):
@shollyman: can we really remove this? It doesn't have "alpha" or "beta" in the path and there's no doc comment saying it's experimental.
|
Current list as of March 3, 2020:
Pub/Sub was the last API blocking CL 50573 |
Connection pooling is now done via transport/grpc.DialPool and is no longer supported with transport/grpc.Dial. See googleapis/google-cloud-go#1777 for the list of packages that will no longer support gRPC connection pooling after this change is merged. Fixes #441 Change-Id: I8e05af53940d6e0af3c2acce9f81b49eaa78bd54 Reviewed-on: https://code-review.googlesource.com/c/google-api-go-client/+/50573 Reviewed-by: kokoro <[email protected]> Reviewed-by: Cody Oss <[email protected]>
The Spanner client library did round-robin connection pooling manually. This changes it to use the new connection pooling in gRPC. This can BREAK user code in the following specific case: * The user specified a value for NumChannels in ClientConfig * The user specified a different value for WithGRPCConnectionPool Example: The following code would work prior to this change, while it will return an error after this change. client, err := NewClientWithConfig( context.Background(), "projects/p/instances/i/databases/d", ClientConfig{NumChannels: 8}, option.WithGRPCConnectionPool(16), ) The example code does however represent a mis-configuration that would break session-channel affiliation, and also would not make any sense. Instead of silently ignoring the mis-configuration and use one of the configured values, the client library now returns an error. This change DEPRECATES ClientConfig.NumChannels. Updates #1777. Change-Id: I14424296cb41f012770186580e9466fec0e5b073 Reviewed-on: https://code-review.googlesource.com/c/gocloud/+/49874 Reviewed-by: kokoro <[email protected]> Reviewed-by: Hengfeng Li <[email protected]>
Is there more to do here still? |
Still remaining:
|
This is required to fully remove refs to gransport.Dial in gocloud. Updates: googleapis/google-cloud-go#1777
This is required to fully remove refs to gransport.Dial in gocloud. Updates: googleapis/google-cloud-go#1777
@shollyman re: bigquery/datatransfer/apiv1/data_source_client: "we can probably just remove it"
The text was updated successfully, but these errors were encountered: