Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of sylvain@datastax.com
 designates 209.85.213.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4E16B04E.1010605@dude.podzone.net>
References: <4E16B04E.1010605@dude.podzone.net>
Date: Fri, 8 Jul 2011 10:18:30 +0200
Message-ID: 
 <CAKkz8Q1JZC=oG0mN7vTxcBocw5J9-=+55PEA1MudMbgyqr_KWw@mail.gmail.com>
Subject: Re: Command Request: rename a column
From: Sylvain Lebresne <sylvain@datastax.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

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.=A0=
 This
> would be extremely powerful, imo.=A0 I suspect the execution would be qui=
ck
> and could even be made atomic (per node) as I suspect it would mostly ent=
ail
> 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 (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.

--
Sylvain