-
Notifications
You must be signed in to change notification settings - Fork 135
feat: make grpc-gcp default enabled #4239
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
base: main
Are you sure you want to change the base?
Conversation
Summary of ChangesHello @rahul2393, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request transitions the Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request makes the grpc-gcp extension enabled by default, which is a good simplification. The changes correctly remove the feature flag and update the related logic. My review includes a few suggestions to improve API clarity and test naming following these changes:
- API Clarity: The methods
enableGrpcGcpExtensionanddisableGrpcGcpExtensionare now misleading or no-ops. I've suggested addressing this to avoid confusion. - Test Naming: Some test method names have become outdated due to the changes. I've pointed these out with suggestions for new names that better reflect their current purpose.
google-cloud-spanner/src/main/java/com/google/cloud/spanner/SpannerOptions.java
Show resolved
Hide resolved
google-cloud-spanner/src/main/java/com/google/cloud/spanner/SpannerOptions.java
Show resolved
Hide resolved
google-cloud-spanner/src/test/java/com/google/cloud/spanner/SpannerOptionsTest.java
Show resolved
Hide resolved
google-cloud-spanner/src/test/java/com/google/cloud/spanner/SpannerOptionsTest.java
Show resolved
Hide resolved
|
@rahul2393 as a first step, can you please enable it by default without removing the option? If needed, customer can disable it. |
4b599e1 to
d2c3101
Compare
8bd7007 to
75ac207
Compare
cd99542 to
eaeef52
Compare
| <artifactId>proto-google-cloud-spanner-admin-database-v1</artifactId> | ||
| <version>6.104.0</version><!-- {x-version-update:proto-google-cloud-spanner-admin-database-v1:current} --> | ||
| </dependency> | ||
| <dependency> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I find this a bit surprising. I would rather have expected this to only be a dependency of com.google.cloud:google-cloud-spanner (so only the actual hand-written client library).
| this.incrementXGoogRequestIdAttempt(); | ||
| Map<SpannerRpc.Option, ?> txChannelHint = getTransactionChannelHint(); | ||
| if (txChannelHint != null && txChannelHint.get(Option.CHANNEL_HINT) != null) { | ||
| long channelHint = Option.CHANNEL_HINT.getLong(txChannelHint); | ||
| this.xGoogRequestId.setChannelId(channelHint); | ||
| } else { | ||
| this.xGoogRequestId.setChannelId(session.getChannel()); | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm.... This is going to conflict with #4263. That PR removes most of the manual handling of Request ID.
| * GOOGLE_CLOUD_SPANNER_MULTIPLEXED_SESSIONS to true in combination with this option, as | ||
| * Multiplexed sessions are not supported for gRPC-GCP. | ||
| */ | ||
| /** Enables gRPC-GCP extension with the default settings. */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| /** Enables gRPC-GCP extension with the default settings. */ | |
| /** Enables gRPC-GCP extension with the default settings. This option is enabled by default. */ |
| if (call.getMethodDescriptor() | ||
| .equals(SpannerGrpc.getBatchCreateSessionsMethod())) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should probably be replaced with CreateSession. It works (for now), but once the session pool is removed, this will silently be ignored, as there are no calls to BatchCreateSessions.
| <dependency> | ||
| <groupId>com.google.cloud</groupId> | ||
| <artifactId>grpc-gcp</artifactId> | ||
| <version>1.7.0</version> | ||
| </dependency> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need it here? AFAICT, it is only used in the hand-written client library (in com.google.cloud:google-cloud-spanner).
|
Note, that, AFAIU, this will also enable grpc-gcp metrics by default (and these are many more metrics than session metrics), this can be an issue if it's shipped to the custom namespace. |
This PR enables the gRPC-GCP channel pool extension by default for Cloud Spanner Java client.
What's Changing for Customers
Before this change
After this change
Benefits of gRPC-GCP
How to Disable gRPC-GCP (Switch Back to GAX Channel Pool)
If you need to disable gRPC-GCP and use the previous GAX channel pooling behavior, use the
disableGrpcGcpExtension()method:When disabled, the default number of channels reverts to 4 (the previous default).
When You Might Want to Disable gRPC-GCP