[
https://issues.apache.org/jira/browse/CASSANDRA-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919453#action_12919453
]
zhu han commented on CASSANDRA-1546:
------------------------------------
{quote}
I wasn't clear in the last comment--the comments were UUID-specific.
{quote}
Kelvin, I was not clear that your questions are UUID-specific. So my question
is generic. No matter UUID is used or not, IMHO, there is read on the write
path. You should get the latest value of local columns (read), and then apply
the increment to it, write the local column to memtable. Sylvain gave detailed
explanation
[here|https://issues.apache.org/jira/browse/CASSANDRA-1546?focusedCommentId=12915683&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12915683].
Although the read of local column is not protected by synchronized block, it
may trigger disk seek and downgrade the performance on write path. Does #1072
has the same problem?
> (Yet another) approach to counting
> ----------------------------------
>
> Key: CASSANDRA-1546
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1546
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Fix For: 0.7.0
>
> Attachments: 0001-Remove-IClock-from-internals.patch,
> 0001-v2-Remove-IClock-from-internals.patch,
> 0001-v3-Remove-IClock-from-internals.txt, 0002-Counters.patch,
> 0002-v2-Counters.patch, 0002-v3-Counters.txt,
> 0003-Generated-thrift-files-changes.patch, 0003-v2-Thrift-changes.patch,
> 0003-v3-Thrift-changes.txt, marker_idea.txt
>
>
> This could be described as a mix between CASSANDRA-1072 without clocks and
> CASSANDRA-1421.
> More details in the comment below.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
