cassandra-commits mailing list archives

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


Jonathan Ellis commented on CASSANDRA-553:

Also, we can't assume that reading the entire row into memory is OK; we want to support larger
rows than memory in 0.9, and even w/o that reading an entire row into memory will cause unwanted
pressure on the rest of the system.

So I think thrift api needs to take a SliceRange to copy, and return a list of column names
copied, so the caller can start the next range (if desired) where the first left off.

> Create copy method in thrift
> ----------------------------
>                 Key: CASSANDRA-553
>                 URL:
>             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,
>   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.

View raw message