Return-Path: 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 5A01A115A4 for ; Tue, 15 Apr 2014 10:40:43 +0000 (UTC) Received: (qmail 43025 invoked by uid 500); 15 Apr 2014 10:40:42 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 42955 invoked by uid 500); 15 Apr 2014 10:40:38 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 42944 invoked by uid 99); 15 Apr 2014 10:40:37 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Apr 2014 10:40:37 +0000 Date: Tue, 15 Apr 2014 10:40:37 +0000 (UTC) From: "Sam Tunnicliffe (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-3680) Add Support for Composite Secondary Indexes 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-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-3680: --------------------------------------- Attachment: (was: 7038-2.1.txt) > Add Support for Composite Secondary Indexes > ------------------------------------------- > > Key: CASSANDRA-3680 > URL: https://issues.apache.org/jira/browse/CASSANDRA-3680 > Project: Cassandra > Issue Type: Sub-task > Reporter: T Jake Luciani > Assignee: Sylvain Lebresne > Labels: cql3, secondary_index > Fix For: 1.2.0 beta 1 > > Attachments: 0001-Secondary-indexes-on-composite-columns.txt > > > CASSANDRA-2474 and CASSANDRA-3647 add the ability to transpose wide rows differently, for efficiency and functionality secondary index api needs to be altered to allow composite indexes. > I think this will require the IndexManager api to have a maybeIndex(ByteBuffer column) method that SS can call and implement a PerRowSecondaryIndex per column, break the composite into parts and index specific bits, also including the base rowkey. > Then a search against a TRANSPOSED row or DOCUMENT will be possible. > -- This message was sent by Atlassian JIRA (v6.2#6252)