Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 28 Aug 2015 10:23:46 +0000 (UTC)
From: "Sam Tunnicliffe (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12857036.1439932734000.192809.1440757426207@Atlassian.JIRA>
In-Reply-To: <JIRA.12857036.1439932734000@Atlassian.JIRA>
References: <JIRA.12857036.1439932734000@Atlassian.JIRA>
 <JIRA.12857036.1439932734890@arcas>
Subject: [jira] [Updated] (CASSANDRA-10124) Support for multi-column indexes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sam Tunnicliffe updated CASSANDRA-10124:
----------------------------------------
    Summary: Support for multi-column indexes  (was: Full support for multi-column and per-row indexes)

> Support for multi-column indexes
> --------------------------------
>
>                 Key: CASSANDRA-10124
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10124
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>              Labels: client-impacting
>             Fix For: 3.0 beta 2
>
>
> Since CASSANDRA-6717 decoupled a secondary index from a single column, we can expand support for indexes with multiple target columns and for row-based indexes with truly dynamic targets.  
> Much of the plumbing for this has been done in CASSANDRA-7771, CASSANDRA-6717 & by the API rework in CASSANDRA-9459. What remains is:
> * Decide on syntax for DDL statements
> * Decide on WHERE clause syntax for SELECT (there is some discussion on this in the comments of CASSANDRA-9459)


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)