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
