[
https://issues.apache.org/jira/browse/CASSANDRA-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779088#action_12779088
]
Vijay commented on CASSANDRA-553:
---------------------------------
In That case we dont need read and write consistency... we just need tow wait
for N nodes to be updated and return back.... for example.... r1, r2 if the
consistency level is Quorum and replicas are 3. If DC quorum we will wait
untill the desired result is recived..... so only one consistency level....
Agree?
Regards
Vijay
> Create copy method in thrift
> ----------------------------
>
> Key: CASSANDRA-553
> URL: https://issues.apache.org/jira/browse/CASSANDRA-553
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Affects Versions: 0.9
> Environment: Cassandra on Linux
> Reporter: Vijay
> Assignee: Vijay
> Priority: Minor
> Fix For: 0.9
>
> Original Estimate: 504h
> Remaining Estimate: 504h
>
> Needed support to Copy method in Cassandra,
> Requirement: Currently users are not allowed to change the Row Key in the
> server side, they need to copy the data @ client. This patch will provide the
> functionality of copying the data using the new RowID (The values will not be
> changed it will be duplicated) @ Cassandra server time.
> The new copy will be using the consistency level.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
