Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4E16D4BC.5090501@dude.podzone.net>
Date: Fri, 08 Jul 2011 03:58:20 -0600
From: AJ <aj@dude.podzone.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
 rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: user@cassandra.apache.org
Subject: Re: Command Request: rename a column
References: <4E16B04E.1010605@dude.podzone.net>
 <CAKkz8Q1JZC=oG0mN7vTxcBocw5J9-=+55PEA1MudMbgyqr_KWw@mail.gmail.com>
In-Reply-To: 
 <CAKkz8Q1JZC=oG0mN7vTxcBocw5J9-=+55PEA1MudMbgyqr_KWw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 7/8/2011 2:18 AM, Sylvain Lebresne wrote:
> On Fri, Jul 8, 2011 at 9:22 AM, AJ<aj@dude.podzone.net>  wrote:
>> I think it would be really cool to be able to rename a column, or, more
>> generally, a move command to move data from one column to another in the
>> same CF without the client having to read and resend the column value.  This
>> would be extremely powerful, imo.  I suspect the execution would be quick
>> and could even be made atomic (per node) as I suspect it would mostly entail
>> only reference updates.
> Cassandra don't work like that. We would have no other choice than to read the
> column and write it back with a different name

I figured as much :)  Not that bad though.

>   (and it would not be atomic). So
> the only win we would get from doing this server side would lie in not
> transferring
> the value across the network.
>

That would be the main benefit I think, esp with large values.

> --
> Sylvain
>