[jira] [Commented] (CASSANDRA-3680) Add Support for Composite Secondary Indexes

["Sylvain Lebresne (Commented) (JIRA)" <ji...@apache.org>]

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

Sylvain Lebresne commented on CASSANDRA-3680:
---------------------------------------------

I think there is two things here: the composite parts and the transposed part. I've created CASSANDRA-3782 to handle the transposed part and to keep this one focused on the composite part. Both issues are not completely unrelated but I feel are sufficiently orthogonal to warrant 2 separate tickets.

I'll note however that for this issue we may want to keep the sparse case in mind. Typically, if I declare:
{noformat}
CREATE TABLE timeline (
   userid uuid,
   posted_at timestamp,
   body text,
   posted_by text,
   PRIMARY KEY (userid, posted_at)
);
{noformat}
then we want to be able to create an index on say posted_by. Which means it's really a PerColumnPrefixSecondaryIndex.
                
> Add Support for Composite Secondary Indexes
> -------------------------------------------
>
>                 Key: CASSANDRA-3680
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3680
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: T Jake Luciani
>              Labels: secondary_index
>
> 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