Details
-
Task
-
Resolution: Fixed
-
Major
-
Cheshire-Cat
-
None
Description
What's the problem?
Currently my understanding is the aim of the existing transactions code was to pass the history generated through the linearizability checker.
As linearizability is a correctness condition for a single object model, I think it's better to test for the serializability consistency model instead.
What's the fix?
Remove the transactions related stuff and reintroduce it in: MB-45690