Interface CassandraBatchOperations

public interface CassandraBatchOperations
Batch operations for insert/update/delete actions on a table. CassandraBatchOperations use logged Cassandra BATCHes for single entities and collections of entities. A CassandraBatchOperations instance cannot be modified/used once it was executed.

Batches are atomic by default. In the context of a Cassandra batch operation, atomic means that if any of the batch succeeds, all of it will. Statement order does not matter within a batch. CassandraBatchOperations applies all rows using the same timestamp if supplied, otherwise Cassandra will generate a timestamp.

Multi partition batches should only be used to achieve atomicity for a few writes on different tables. Apart from this they should be avoided because they’re too expensive. Single partition batches can be used to get atomicity and isolation, they're not much more expensive than normal writes.

Mark Paluch, Anup Sabbi