Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 6 Aug 2012 19:48:03 +0000 (UTC)
From: "Yuki Morishita (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <1220210733.18024.1344282483354.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <1869732237.49403.1325107290650.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CASSANDRA-3680) Add Support for Composite
 Secondary Indexes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13429377#comment-13429377 ] 

Yuki Morishita commented on CASSANDRA-3680:
-------------------------------------------

hmm, filtering with key and 2I works, but this time I get wrong value for key.

{code}
cqlsh:3680> select * from blogs;
 blog_id | posted_at                | author | content
---------+--------------------------+--------+---------
       1 | 2012-11-11 00:00:00-0600 |    foo |     bar
       2 | 2012-11-12 00:00:00-0600 |    foo |     baz
       3 | 2012-11-11 00:00:00-0600 |    qux |    quux

cqlsh:3680> select * from blogs where author='foo' and posted_at = '2012-11-11';
 blog_id | posted_at                | author | content
---------+--------------------------+--------+---------
       2 | 2012-11-11 00:00:00-0600 |    foo |     bar
{code}

blog_id should be '1'.

{code}
cqlsh:3680> select * from blogs where author='foo';
 blog_id | posted_at                | author | content
---------+--------------------------+--------+---------
       2 | 2012-11-11 00:00:00-0600 |    foo |     bar
       2 | 2012-11-12 00:00:00-0600 |    foo |     baz
{code}

Here, something is wrong with first row in result set.
                
> 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
>
>         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 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