On Thu, Jun 5, 2014 at 2:38 PM, Charlie Mason wrote:
>
> I can't do the initial account insert with a TTL as I can't guarantee when
> a new value would come along and so replace this account record. However
> when I insert the new account record, instead of deleting the old one could
> I reinsert
thinking about for that sort of batch
> updating?
>
>
> James Campbell
> ------------------
> *From:* Aaron Morton
> *Sent:* Thursday, June 5, 2014 5:26 AM
> *To:* Cassandra User
> *Cc:* charlie@gmail.com
> *Subject:* Re: Consolidating records an
I should be
thinking about for that sort of batch updating?
James Campbell
From: Aaron Morton
Sent: Thursday, June 5, 2014 5:26 AM
To: Cassandra User
Cc: charlie@gmail.com
Subject: Re: Consolidating records and TTL
As Tyler says, with atomic batches which ar
As Tyler says, with atomic batches which are enabled by default the cluster
will keep trying to replay the insert / deletes.
Nodes check their local batch log for failed batches, ones where the
coordinator did not acknowledge it had successfully completed, every 60
seconds. So there is a windo
Just use an atomic batch that holds both the insert and deletes:
http://www.datastax.com/dev/blog/atomic-batches-in-cassandra-1-2
On Tue, Jun 3, 2014 at 2:13 PM, Charlie Mason wrote:
> Hi All.
>
> I have a system thats going to make possibly several concurrent changes to
> a running total. I kn
Hi All.
I have a system thats going to make possibly several concurrent changes to
a running total. I know I could use a counter for this. However I have
extra meta data I can store with the changes which would allow me to reply
the changes. If I use a counter and it looses some writes I can't rec
