Logged BATCH atomicity

ScyllaDB
, , ,
1

Hi everyone,

I’m using denormalized tables with different partition keys (e.g., orders_by_order_id, orders_by_customer_id by customer_id, orders_by_merchant_id by merchant_id).

When I write to all three tables using a logged BATCH:

BEGIN BATCH
   INSERT INTO orders (order_id, ...) VALUES (...);
   INSERT INTO orders_by_customer_id (customer_id, order_id, ...) VALUES (...);
   INSERT INTO orders_by_merchant_id (merchant_id, order_id, ...) VALUES (...);
APPLY BATCH;

This pattern is also mentioned “ScyllaDB in action”, chapter 6.4.

My Questions:

The batch will be executed against 3 different tables with 3 different partition keys. Will the batch log ensure ALL three inserts eventually succeed, or can some succeed while others fail permanently?