Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Cassandra batch operations [DATACASS-288] #459

spring-projects-issues opened this issue May 21, 2016 · 1 comment


Copy link

@spring-projects-issues spring-projects-issues commented May 21, 2016

Mark Paluch opened DATACASS-288 and commented

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.

interface CassandraBatchOperations {

  void execute();

  CassandraBatchOperations <T> insert(T entity);
  CassandraBatchOperations <T> insert(Iterable<T> entities);

  CassandraBatchOperations <T> update(T entity);
  CassandraBatchOperations <T> update(Iterable<T> entities);

  CassandraBatchOperations <T> delete(T entity);
  CassandraBatchOperations <T> delete(Iterable<T> entities);

Issue Links:

  • DATACASS-289 Use multiple statements instead of batches for multi-row operations in CassandraTemplate
    ("is depended on by")

Referenced from: pull request #78, and commits d0610b2, e818d3b

Copy link

@spring-projects-issues spring-projects-issues commented Jul 25, 2016

John Blum commented

PR #78 merged to master for the Ingalls, 1.5 M1 release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants