I have seen this question pop up once or twice in mailing lists regarding
atomicity when using batch_mutate() operations. I understand that the
operations in batch_mutate() should be idempotent and do not get rolled back
on failures. However, a client crashing (due to machine issues, networking
issue etc) in the middle of such a transaction can leave the data in an
inconsistent state. Is there a way to figure out such inconsistencies ? Will
Cassandra keep a log of failed batch_mutate() operations, or partially
completed operations, that might require manual intervention when the client
comes back up ?
