Any pointers on this?.
In 2.1, when updating the counter with UNLOGGED batch using timestamp isn't safe as other column update with consistency level (with timestamp counter update can be idempotent? ).
On 09-Jul-2015 11:47 am, "Ajay" <firstname.lastname@example.org> wrote:
> What is the accuracy improvement of counter in 2.1 over 2.0?
> This below post, it mentioned 2.0.x issues fixed in 2.1 and perfomance improvement.
> But how accurate are the counter 2.1.x or any known issues in 2.1 using UNLOGGED batch for counter update with timestamp?