fix(spanner): check for empty before delete (#4047)#4077
Merged
Conversation
spanner IT fails for `deleteAllById_doesNothingOnEmptyIds` test with error from Spanner: `INVALID_ARGUMENT: Failed to initialize transaction due to invalid mutation key.` **Trigger of this behavior change:** spanner activated multiplexed sessions by default in [googleapis/java-spanner#3996](googleapis/java-spanner#3996), which triggers this error. When issuing a write() with a Mutation that has an empty KeySet produces an exception in Multiplexed clients (see [pr](googleapis/java-spanner#4023)), but does a no-op in non-multiplexed ones. Unlike Regular session, multiplex session needs a valid mutation to generate a precommit token. Fixes #4046
diegomarquezp
approved these changes
Aug 19, 2025
mpeddada1
approved these changes
Aug 19, 2025
|
zhumin8
pushed a commit
that referenced
this pull request
Aug 20, 2025
🤖 I have created a release *beep* *boop* --- ## [6.3.2](v6.3.1...v6.3.2) (2025-08-19) ### Bug Fixes * **spanner:** check for empty before delete ([#4047](#4047)) ([#4077](#4077)) ([cb1f687](cb1f687)), closes [#4046](#4046) ### Dependencies * bump com.google.cloud:libraries-bom from 26.65.0 to 26.66.0 ([#4067](#4067)) ([970c11c](970c11c)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). --------- Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
backport fix from #4047
spanner IT fails for
deleteAllById_doesNothingOnEmptyIdstest with error from Spanner:INVALID_ARGUMENT: Failed to initialize transaction due to invalid mutation key.Trigger of this behavior change:
spanner activated multiplexed sessions by default in googleapis/java-spanner#3996, which triggers this error. When issuing a write() with a Mutation that has an empty KeySet produces an exception in Multiplexed clients (see pr), but does a no-op in non-multiplexed ones. Unlike Regular session, multiplex session needs a valid mutation to generate a precommit token.
Fixes #4046