You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2013/02/20 06:01:15 UTC

[jira] [Resolved] (CASSANDRA-3782) Secondary indexes support for wide rows in CQL 3.0

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

Sylvain Lebresne resolved CASSANDRA-3782.
-----------------------------------------

    Resolution: Won't Fix

I'm going to close that one because I think CASSANDRA-5125 pretty much give us
what we want here for CQL3.
                
> Secondary indexes support for wide rows in CQL 3.0
> --------------------------------------------------
>
>                 Key: CASSANDRA-3782
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3782
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: API
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>             Fix For: 1.2.2
>
>
> Currently, CQL 3.0 doesn't allow creating an index on a dynamic CF (with COMPACT STORAGE). The goal of this ticket is *not* to support the composite case however (CASSANDRA-3680 will tackle this).
> I think changes needed to support this are only in the CQL side and covert two area:
> * Finding a syntax for it
> * Currently, the CQL 3 code consider that a CF with any column_metadata defined is a non-compact cf. Basically the problem is that we currently use column_metadata both for defining a name for a column in the static case, and store indexing information. Ideally, we would separate those informations, i.e. we could add a new map valueAliases (ByteBuffer -> AbstractType) to CFMetadata (only used by static CF) and we would keep column_metadata for indexing purpose only. However that may be problematic for backward compatibility (with thrift in particular), so probably instead we can just add a new boolean isStaticColumnName to ColumnDefinition.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira