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.214.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAA_K6YuT5-GwEXrxkwfoFRfZDr6vbyMVp_0WyyecKBZ30g_zcQ@mail.gmail.com>
References: 
 <CAA_K6YuT5-GwEXrxkwfoFRfZDr6vbyMVp_0WyyecKBZ30g_zcQ@mail.gmail.com>
Date: Tue, 24 Jul 2012 12:11:54 +0200
Message-ID: 
 <CAKkz8Q1+emY=_h1FoQy9VaW1mNfiufr=Yx5AJwpHe0MEUOYDKA@mail.gmail.com>
Subject: Re: CQL3 and column slices
From: Sylvain Lebresne <sylvain@datastax.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jul 24, 2012 at 12:09 AM, Josep Blanquer
<blanquer@rightscale.com> wrote:
> is there some way to express that in CQL3? something logically equivalent to
>
> SELECT *  FROM bug_test WHERE a:b:c:d:e > 1:1:1:1:2    ??

No, there isn't. Not currently at least. But feel free of course to
open a ticket/request on
https://issues.apache.org/jira/browse/CASSANDRA.

I note that I would be curious to know the concrete use case you have
for such type of queries. It would also help as an argument to add
such facilities more quickly (or at all). Typically, "we should
support it in CQL3 because it was possible with thrift" is
definitively an argument, but a much weaker one without concrete
examples of why it might be useful in the first place.

--
Sylvain