cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-553) Create copy method in thrift
Date Thu, 17 Dec 2009 18:33:18 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792053#action_12792053
] 

Jonathan Ellis commented on CASSANDRA-553:
------------------------------------------

01: I rebased again for you as penance for taking so long to review

02: cleaned up the style to match our guidelines better.  please follow these in future patches

03: sketched out some fixes the actual copy work.  basically, for each target you want to
copy from the closest source to it, the closest source to the "command" node will not necessarily
have the same order.  Then you tell each source node the list of target nodes to copy to.
 standard WriteResponseHandler won't work as-is, since each source node is doing potentially
multiple copies.  So you need to extend WRH or create a new CopyResponseHandler; probably
the former is easier.

Other stuff:
- CopyVerbHandler needs to handle HH to nodes that are down


> 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
>
>         Attachments: 0001-fix-conflicts.txt, 0002-style-fixes.txt, 0003-sketch-out-fixes.txt,
Copy-Command.patch
>
>   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.


Mime
View raw message