[
https://issues.apache.org/jira/browse/CASSANDRA-7688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14307114#comment-14307114
]
Aleksey Yeschenko commented on CASSANDRA-7688:
----------------------------------------------
Since it's a single partition update, the whole thing is atomic and isolated,
yes. I'm adding updates to the mutation one by one, but applying everything,
including the removal of previous state, and addition of the new data, in one
go, at mutation.apply() point.
So long as you fetch all the ranges together in one query, you'll always have a
complete state. It might be slightly out of date and lagging behind (rare)
topology updates for up to 5 minutes, but it'll always be internally consistent.
> Add data sizing to a system table
> ---------------------------------
>
> Key: CASSANDRA-7688
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7688
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Jeremiah Jordan
> Assignee: Aleksey Yeschenko
> Fix For: 2.1.3
>
> Attachments: 7688.txt
>
>
> Currently you can't implement something similar to describe_splits_ex purely
> from the a native protocol driver.
> https://datastax-oss.atlassian.net/browse/JAVA-312 is open to expose easily
> getting ownership information to a client in the java-driver. But you still
> need the data sizing part to get splits of a given size. We should add the
> sizing information to a system table so that native clients can get to it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
