All geek questions in one place

Astyanax: If MutationBatch doesn't work halfway, what guarantees do I have?

I know that with 0.8 Cassandra ensures that row updates are atomic.

However, if I prepare (using MutationBatch) several modifications or modifications of a series in several column families, is it guaranteed that the rows will be updated in the order in which I set them? For example, if I have

  • CF Update 1, Line 1
  • CF Update 1, Line 2
  • CF Update 2, Line 3

Is CF 2 upgrade possible while CF 1 remains unchanged due to failure?

What happens if I install:

  • CF Update 1, Row 1, Column A
  • CF Update 1, Line 2
  • CF Update 2, Line 3
  • CF Update 1, Line 1, Column B

Alternatively, should you prepare three MutationBatches instead and execute them separately?

+2
source share
2 answers

All updates are performed in parallel, so the order is not guaranteed. Partial success will result in batchlog taking and ending the game starting at 1.2: http://www.datastax.com/dev/blog/atomic-batches-in-cassandra-1-2

+2
source

Playorm supports flash support, which pushes all your stubbornness down with one shot, so it kind of sends it as a unit of work (NOT a transaction).

http://buffalosw.com/wiki/flush-support/

+1
source

Source: https://habr.com/ru/post/1310491/

More articles:


All Articles