Skip to content

chore(spanner): Implement fallback for multiplexed session on Partitioned Operations #3631

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

Merged
merged 10 commits into from
Feb 18, 2025
Merged

chore(spanner): Implement fallback for multiplexed session on Partitioned Operations #3631

merged 10 commits into from
Feb 18, 2025

Conversation

pratickchokhani
Copy link
Contributor

  • handle server side kill switch for multiplexed sessions with Partitioned Ops.

…oned Operations

- handle server side kill switch for multiplexed sessions with Partitioned Ops.
@pratickchokhani pratickchokhani requested review from a team as code owners February 10, 2025 15:08
@product-auto-label product-auto-label bot added size: m Pull request size is medium. api: spanner Issues related to the googleapis/java-spanner API. labels Feb 10, 2025
}

void maybeMarkUnimplementedForPartitionedOps(SpannerException spannerException) {
if (spannerException.getErrorCode() == ErrorCode.INVALID_ARGUMENT
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you sure that the error code will be INVALID_ARGUMENT (and not UNIMPLEMENTED)?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, for Partitioned Read or Query, we are returning INVALID_ARGUMENT.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pratickchokhani
As discussed in the meeting, can we temporarily remove the error code check?

Context:
We plan to update the backend to return the UNIMPLEMENTED error for partitioned operations. However, this change will not be part of the current release and will be introduced in a follow-up update.

If we proceed with this error code check now, it will break backward compatibility when the backend starts returning UNIMPLEMENTED. To avoid this issue, we are removing the check for now and will reintroduce it once the backend update is complete.

cc: @rahul2393 to do the same for golang.

@harshachinta
Copy link
Contributor

@pratickchokhani
Please fix the error code discussion before merging this commit.

@pratickchokhani pratickchokhani merged commit 1b4b4d3 into googleapis:main Feb 18, 2025
32 of 33 checks passed
@suztomo suztomo mentioned this pull request Mar 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: spanner Issues related to the googleapis/java-spanner API. size: m Pull request size is medium.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants