CassandraTemplate DML operations affecting multiple rows (e.g. insert(List<T> entities)) use Cassandra batches without the possibility of issuing just multiple inserts/updates/deletes. Batches should get a dedicated interface to execute and give control to the caller. So the caller can decide whether to use batches and which type of batch to use. The API should omit UNLOGGED batches as unlogged batches are deprecated with Cassandra 3.0.
Switching CassandraTemplate from batch operations to issuing multiple commands is not part of this ticket.