Cool... Okay, the plan is to eventually not use thrift underneath, for the
CQL stuff right?
Once this is done and the new transport is in place, or evening while
designing the new transport,
is this not something that's worth looking into again? I think it'd be a
nice feature.
-----Original Message-----
From: Jonathan Ellis
Sent: Monday, April 18, 2011 3:24 AM
To: user@cassandra.apache.org
Cc: Tyler Hobbs
Subject: Re: CQL DELETE statement
Very old. https://issues.apache.org/jira/browse/CASSANDRA-494
On Sun, Apr 17, 2011 at 7:49 PM, Tyler Hobbs <ty...@datastax.com> wrote:
You are correct, but this is also a limitation with the Thrift API -- it's
not CQL specific. It turns out that deleting a slice of columns is
difficult. There's an old JIRA ticket somewhere that describes the
issues.
On Sun, Apr 17, 2011 at 7:45 PM, Courtney Robinson <sa...@live.co.uk>
wrote:
Looking at the CQL spec, it doesn’t seem to be possible to delete a range
of columns for a given key without specifying the individual columns to
be
removed, for e.g.
DELETE col1 .. col20 from CF WHERE KEY=<key|(key1,key2)>
Am I correct in thinking so or have I missed that somewhere?
--
Tyler Hobbs
Software Engineer, DataStax
Maintainer of the pycassa Cassandra Python client library
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
