batches:
https://docs.datastax.com/en/cql/3.3/cql/cql_reference/cqlCreateTable.html#tabProp__cqlTableGc_grace_seconds
/pelle
From: Maxim Parkachov
Sent: den 20 augusti 2018 08:29
To: user@cassandra.apache.org
Subject: Re: Repair daily refreshed table
Hi Raul,
I cannot afford delete and then load
Hi Raul,
I cannot afford delete and then load as this will create downtime for the
record, that's why I'm upserting with TTL today()+7days as I mentioted in
my original question. And at the moment I don't have an issue either with
loading nor with access times. My question is should I repair such
If you wanted to be certain that all replicas were acknowledging receipt of the
data, then you could use ALL or EACH_QUORUM ( if you have multiple DCs) but you
must really want high consistency if you do that.
You should avoid consciously creating tombstones if possible — it ends up
making read
Hi Rahul,
I'm already using LOCAL_QUORUM in batch process and it runs every day. As
far as I understand, because I'm overwriting whole table with new TTL,
process creates tons of thumbstones and I'm more concerned with them.
Regards,
Maxim.
On Sun, Aug 19, 2018 at 3:02 AM Rahul Singh
wrote:
>
Are you loading using a batch process? What’s the frequency of the data Ingest
and does it have to very fast. If not too frequent and can be a little slower,
you may consider a higher consistency to ensure data is on replicas.
Rahul
On Aug 18, 2018, 2:29 AM -0700, Maxim Parkachov , wrote:
> Hi c
