Return-Path: 
 <commits-return-58304-apmail-cassandra-commits-archive=cassandra.apache.org@cassandra.apache.org>
X-Original-To: apmail-cassandra-commits-archive@www.apache.org
Delivered-To: apmail-cassandra-commits-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id B6A25C6DB
	for <apmail-cassandra-commits-archive@www.apache.org>;
 Sun, 12 Aug 2012 22:34:38 +0000 (UTC)
Received: (qmail 89574 invoked by uid 500); 12 Aug 2012 22:34:38 -0000
Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org
Received: (qmail 89541 invoked by uid 500); 12 Aug 2012 22:34:38 -0000
Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@cassandra.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@cassandra.apache.org>
List-Post: <mailto:commits@cassandra.apache.org>
List-Id: <commits.cassandra.apache.org>
Reply-To: dev@cassandra.apache.org
Delivered-To: mailing list commits@cassandra.apache.org
Received: (qmail 89529 invoked by uid 99); 12 Aug 2012 22:34:38 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 12 Aug 2012 22:34:38 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 19ED52C5ACF
	for <commits@cassandra.apache.org>; Sun, 12 Aug 2012 22:34:38 +0000 (UTC)
Date: Mon, 13 Aug 2012 09:34:38 +1100 (NCT)
From: "Vijay (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <1600404973.128.1344810878106.JavaMail.jiratomcat@arcas>
In-Reply-To: 
 <1932155836.44969.1306405187356.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (CASSANDRA-2710) Get multiple column ranges
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/CASSANDRA-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vijay updated CASSANDRA-2710:
-----------------------------

    Attachment: 0001-2710-multiple-column-ranges-thrift.patch
    
> Get multiple column ranges
> --------------------------
>
>                 Key: CASSANDRA-2710
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2710
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: David Boxenhorn
>            Assignee: Vijay
>              Labels: compositeColumns, cql
>         Attachments: 0001-2710-multiple-column-ranges-thrift.patch
>
>
> I have replaced all my super column families with regular column families using composite columns. I have easily been able to support all previous functionality (I don't need range delete) except for one thing: getting multiple super columns with a single access. For this, I would need to get multiple ranges. (I can get multiple columns, or a single range, but not multiple ranges.) 
> For example, I used to have
> [<superColumnName1>,<subColumnName1..N>],[<superColumnName2>,<subColumnName1..N>]
> and I could get superColumnName1, superColumnName2
> Now I have
> [<len><superColumnName1>0<len><subColumnName1>..<len><superColumnName1>0<len><subColumnNameN>],[<len><superColumnName2>0<len><subColumnName1>..<len><superColumnName2>0<len><subColumnNameN>]
> and I need to get superColumnName1..superColumnName1+, superColumnName2..superColumnName2+
> to get the same functionality
> I would like the clients to support this functionality, e.g. Hector to have .setRages parallel to .setColumnNames 
> and for CQL to support a syntax like 
> SELECT [FIRST N] [REVERSED] name1..nameN1, name2..nameN2... FROM ...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira