IGNITE-28610 Implement savepoint for Key-Value API for pessimistic transactions #13080
Conversation
…sibility issue in transactional replication cache with one backup and near.
1795449 to
37c8156
Compare
…e name already exists or does not exist.
|
|
||
| /** Savepoint rollback flag. */ | ||
| @Order(1) | ||
| public boolean forSavepoint; |
There was a problem hiding this comment.
Check Rolling Upgrade check suggests there might be a problem. Let's figure out what might be wrong with the feature authors.
There was a problem hiding this comment.
I do not see an issue with this change from the point of view of rolling upgrades. As I understand it, Ignite can update only by restarting on the same storage; this PR does not touch persistence classes.
What do you think can be wrong?
Possible compatibility issues. Please, check rolling upgrade casesThis PR modifies protected classes (with Order annotation). Affected files:
|
|




https://issues.apache.org/jira/browse/IGNITE-28610