How to guarantee consistency between counter and materialized view?

[ziju feng <pk...@gmail.com>]

Hi all,

Is there any way to guarantee a counter's value in materialized views,
which could be some other column families with different row keys and with
counter's value de-normalized, in sync with the value in its counter column
family?

Since batch can only work as either non-counter or counter-only batch, I
can't have updating the batch table and the materialized view tables in one
batch. In the case that the client fails right after updating the counter
table and right before updating the materialized views, there could be
inconsistent data.

Thanks,

Ziju

Re: How to guarantee consistency between counter and materialized view?

[Oleg Dulin <ol...@gmail.com>]

Robert Coli <rc...@eventbrite.com> wrote:
> On Tue, Mar 11, 2014 at 4:30 PM, ziju feng <pk...@gmail.com> wrote:
> 
> Is there any way to guarantee a counter's value
> 
> no.
> 
> =Rob

I wouldn't use cassandra for counters... Use something like redis if that
is what you want.

Re: How to guarantee consistency between counter and materialized view?

[Robert Coli <rc...@eventbrite.com>]

On Tue, Mar 11, 2014 at 4:30 PM, ziju feng <pk...@gmail.com> wrote:

> Is there any way to guarantee a counter's value
>

no.

=Rob