You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Lex Lythius (JIRA)" <ji...@apache.org> on 2014/11/06 19:08:35 UTC
[jira] [Commented] (CASSANDRA-4511) Secondary index support for
CQL3 collections
[ https://issues.apache.org/jira/browse/CASSANDRA-4511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14200569#comment-14200569 ]
Lex Lythius commented on CASSANDRA-4511:
----------------------------------------
Note that CQL for Cassandra 2.x documentation (page 48) still says:
{quote}Currently, you cannot create an index on a column of type map, set, or list.{quote}
whereas CREATE INDEX syntax is accurate:
{code}
CREATE CUSTOM INDEX IF NOT EXISTS index_name
ON keyspace_name.table_name ( KEYS ( column_name ) )
(USING class_name) (WITH OPTIONS = map)
{code}
> Secondary index support for CQL3 collections
> ---------------------------------------------
>
> Key: CASSANDRA-4511
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4511
> Project: Cassandra
> Issue Type: Improvement
> Affects Versions: 1.2.0 beta 1
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Fix For: 2.1 beta1
>
> Attachments: 4511.txt
>
>
> We should allow to 2ndary index on collections. A typical use case would be to add a 'tag set<String>' to say a user profile and to query users based on what tag they have.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)