sirikata/sirikata — Issue #494: CassandraStorage doesn't roll back failed transactions
Author: ewencp
Created: 2012-02-09 02:37:26+00:00
State: open

CassandraStorage just processes the parts of transactions one at a time, which doesn't match the transactional semantics required by the OH::Storage interface. 8fdf319003ee9fdb87e26ee9528f1c2d3da23729 introduces a test which shows how the failure can occur. Just ordering mutation operations last isn't sufficient since, e.g., the last mutation could fail.

If Cassandra can't implement this directly, we might need to build a layer on top of Cassandra which can do these multi-key updates. Note that this may have also become a bit more complicated with the compare operations added in f88435fcd4d329af387dcf3b7fe08436ca969cc7.