IGNITE-24436 Do not clean index on tx cleanup if no index info is available #5223
+58
−7
Conversation
This file contains 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
Phillippko
force-pushed
the
ignite-24436
branch
from
4a84c1a to
786de8b
Compare
rpuch
approved these changes
Feb 13, 2025
...a/org/apache/ignite/internal/table/distributed/replication/PartitionReplicaListenerTest.java
Outdated
Show resolved
Hide resolved
rpuch
approved these changes
Feb 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Couldn't reproduce with an integration test, so extracted to another issue. Simple unit-test introduced instead
For write-switch intents replaced method throwing an exception if catalog version was not found with a method, returning null value. When null indexIds are passed to StorageUpdateHandler, it tries to update all currently available indexes (only for commit). It is better than skipping indexes completely