sirikata/sirikata — Issue #495: CassandraStorage doesn't properly implement transactions
Author: ewencp
Created: 2012-02-09 02:39:08+00:00
State: open

This is related to #494 . The storage implementations should ensure that entire transactions are truly atomic. The proper rollback that #494 talks about improves things, but doesn't work if two nodes try to access the backend store at the same time. However, it's possible the same fix could address this issue as well.

A test for this would be ideal, but may not be easy to fit into the current unit test framework since transactions for a single object could just be handled in order. Multiple processes may be necessary to properly test for correctness.