[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-tabpanelfocusedCommentId=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 setString' 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)
[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-tabpanelfocusedCommentId=14200624#comment-14200624 ] Kristine Hahn commented on CASSANDRA-4511: -- Thanks, [~lexlythius]. http://www.datastax.com/documentation/cql/3.1/cql/cql_reference/collection_type_r.html 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 setString' 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)
[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-tabpanelfocusedCommentId=13869432#comment-13869432 ] Naresh Yadav commented on CASSANDRA-4511: - @Russ Hatch taken source code today and I am also facing exactly same issue..insert,select not working but insert,update tags,select works..Please share if you have fix for this.. 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 Attachments: 4511.txt We should allow to 2ndary index on collections. A typical use case would be to add a 'tag setString' to say a user profile and to query users based on what tag they have. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[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-tabpanelfocusedCommentId=13869641#comment-13869641 ] Sylvain Lebresne commented on CASSANDRA-4511: - Alright, thanks for the testing Russ. I'll look what's going on but let's reopen in the meantime so I don't forget 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 Attachments: 4511.txt We should allow to 2ndary index on collections. A typical use case would be to add a 'tag setString' to say a user profile and to query users based on what tag they have. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[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-tabpanelfocusedCommentId=13868543#comment-13868543
]
Russ Hatch commented on CASSANDRA-4511:
---
I'm running into a bit of trouble testing here. When indexing a list column,
and providing a list literal at insert, I get no results back when querying
using contains. If create the row without the list, then do an update to add
the list, the query returns the expected result.
basic steps to reproduce:
{noformat}
I'm working with a single node. I tried the test below with a listtext and
listuuid types and get the same behavior.
Connected to test_cluster at 127.0.0.1:9160.
[cqlsh 4.1.1 | Cassandra 2.1-SNAPSHOT | CQL spec 3.1.1 | Thrift protocol
19.39.0]
Use HELP for help.
cqlsh create keyspace list_index_search with replication =
{'class':'SimpleStrategy', 'replication_factor':1} ;
cqlsh CREATE TABLE list_index_search.users (
... user_id uuid PRIMARY KEY,
... email text,
... tags listtext
... );
cqlsh CREATE INDEX user_uuids on list_index_search.users (tags);
cqlsh INSERT INTO list_index_search.users (user_id, email, tags)
... values (370e0d97-9c23-4718-9f74-ac5778bd8636, 't...@example.com',
['awesome']);
cqlsh select * from list_index_search.users where tags contains 'awesome';
-- aargh, no rows!
(0 rows)
cqlsh UPDATE list_index_search.users SET tags = ['awesome'] where user_id =
370e0d97-9c23-4718-9f74-ac5778bd8636;
cqlsh select * from list_index_search.users where tags contains 'awesome';
user_id | email| tags
--+--+-
370e0d97-9c23-4718-9f74-ac5778bd8636 | t...@example.com | ['awesome']
(1 rows)
cqlsh
{noformat}
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
Attachments: 4511.txt
We should allow to 2ndary index on collections. A typical use case would be
to add a 'tag setString' to say a user profile and to query users based on
what tag they have.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[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-tabpanelfocusedCommentId=13837159#comment-13837159 ] Aleksey Yeschenko commented on CASSANDRA-4511: -- LGTM nit: ExtendedFilter.findValueInCollection() is unused 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 Attachments: 4511.txt We should allow to 2ndary index on collections. A typical use case would be to add a 'tag setString' to say a user profile and to query users based on what tag they have. -- This message was sent by Atlassian JIRA (v6.1#6144)
[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-tabpanelfocusedCommentId=13829693#comment-13829693 ] Aleksey Yeschenko commented on CASSANDRA-4511: -- CONTAINS WFM as well. [~slebresne] If the patch is reviewable in the current form, and doesn't need any modifications post all the discussion, can you please switch the issue to Patch Available (with a rebased patch if necessary)? Thanks. 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 Attachments: 4511.txt We should allow to 2ndary index on collections. A typical use case would be to add a 'tag setString' to say a user profile and to query users based on what tag they have. -- This message was sent by Atlassian JIRA (v6.1#6144)
[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-tabpanelfocusedCommentId=13827651#comment-13827651 ] Jonathan Ellis commented on CASSANDRA-4511: --- bq. how do you index the 'y' field of the values in 'x' Yeah, that's where I was going. I note that mongodb only allows indexing top-level fields: http://docs.mongodb.org/manual/core/index-single/ http://docs.mongodb.org/manual/core/index-multikey/ Created CASSANDRA-6382 for indexing user types with dot notation. Let's skip the collections complication. (Does sound like we have a consensus for indexing map keys.) 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 Attachments: 4511.txt We should allow to 2ndary index on collections. A typical use case would be to add a 'tag setString' to say a user profile and to query users based on what tag they have. -- This message was sent by Atlassian JIRA (v6.1#6144)
[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-tabpanelfocusedCommentId=13827676#comment-13827676 ] Sylvain Lebresne commented on CASSANDRA-4511: - bq. Does sound like we have a consensus for indexing map keys. Yep, but as said above, I'd rather tackle the remaining bits of that in CASSANDRA-6383 since there a few added difficulties related to the 2ndary index API. We do need to decide though, do we stick to CONTAINS here (and use CONTAINS KEY in CASSANDRA-6383) or do we prefer IN (and we need a new idea for CASSANDRA-6383). I personally have a slight preference for CONTAINS just because the extension to map keys seems more straightforward, but I don't care a whole lot otherwise. 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 Attachments: 4511.txt We should allow to 2ndary index on collections. A typical use case would be to add a 'tag setString' to say a user profile and to query users based on what tag they have. -- This message was sent by Atlassian JIRA (v6.1#6144)
[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-tabpanelfocusedCommentId=13827681#comment-13827681 ] Jonathan Ellis commented on CASSANDRA-4511: --- CONTAINS WFM. 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 Attachments: 4511.txt We should allow to 2ndary index on collections. A typical use case would be to add a 'tag setString' to say a user profile and to query users based on what tag they have. -- This message was sent by Atlassian JIRA (v6.1#6144)
[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-tabpanelfocusedCommentId=13826309#comment-13826309
]
Sylvain Lebresne commented on CASSANDRA-4511:
-
bq. How could this extend to user types?
Technically, we'd need versions of the existing CompositesIndex (the one on
regular columns and the 2 new ones introduced by this patch for user types
within collections) that knows how to reach into the value to find the actual
value indexed. But that should be fairly straightforward.
Syntax-wise, that's a harder problem :). For user types not in a collection,
the simplest solution seems to just use the dot notation (so SELECT * FROM bar
WHERE x.y = 'foo') but I suppose your meant user types in collections, i.e,
given
{noformat}
CREATE USER TYPE sometype (y text, z text)
CREATE TABLE bar (k int PRIMARY KEY, x setsometype)
{noformat}
how do you index the 'y' field of the values in 'x'. In which case I don't
really have a good syntax to offer so far, not even to declare the index in the
first place. Maybe we'd have to resort to some sort of variable binding,
something like
{noformat}
SELECT * FROM bar WHERE $e.y = 'foo' FOR $e IN x
{noformat}
(where I use a '$' to make it clear that '$e' would just be some form of
query-local variable but we can do without it)
bq. Since maps are basically one of the big replacements for dynamic columns
Oh My...
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
Attachments: 4511.txt
We should allow to 2ndary index on collections. A typical use case would be
to add a 'tag setString' to say a user profile and to query users based on
what tag they have.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[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-tabpanelfocusedCommentId=13825335#comment-13825335 ] Sylvain Lebresne commented on CASSANDRA-4511: - bq. I'm struggling to think of a use case for indexing map keys One thing that comes into mind is tags, but where you want to attach some data to it. Say, when was the tag added, or maybe whom added it. In that case, you could imagine wanting to index both the keys (the tag itself, to know what object has tag X) and the values (for instance to know 'which object did user Y tagged'). And btw, technically there is not a whole lot of difficulty adding this, we just need to go a bit over the 2ndary index API to make sure we can add more than one index on a given name. But that API probably need some cleanup anyway. bq. Also, it occurs to me that we don't need to add new syntax True. But I'll note that 1) we don't, technically speaking, support this syntax currently, we only support 'IN ?' and 'IN (...)', so it save adding one token to the lexer but doesn't entirely save from updating the grammar and 2) internally, I still think we'd want to keep it a separate case from other IN because it has different rules anyway. Overall, I don't mind using IN over CONTAINS if we think that's a better syntax but I don't think one of the arguments should be because it makes things easier internally (didn't meant to imply this was your argument btw, just making sure we agree on why we would make the choice) because I don't think that's true. In any case, as far as I'm concerned, I don't care a whole lot between CONTAINS and IN, expect maybe that it feels easier to extend the syntax to map keys with CONTAINS (using CONTAINS KEY). 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 Attachments: 4511.txt We should allow to 2ndary index on collections. A typical use case would be to add a 'tag setString' to say a user profile and to query users based on what tag they have. -- This message was sent by Atlassian JIRA (v6.1#6144)
[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-tabpanelfocusedCommentId=13825504#comment-13825504 ] Jonathan Ellis commented on CASSANDRA-4511: --- How could this extend to user types? 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 Attachments: 4511.txt We should allow to 2ndary index on collections. A typical use case would be to add a 'tag setString' to say a user profile and to query users based on what tag they have. -- This message was sent by Atlassian JIRA (v6.1#6144)
[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-tabpanelfocusedCommentId=13825918#comment-13825918
]
Zachary Marcantel commented on CASSANDRA-4511:
--
I can think of (and need this for) a few use cases. They do revolve around more
of a filtering aspect, however.
It can be said that sometimes models/data/rows belong to a theoretical list
that contain infinite possibilities.
Naturally, you do not want to store all possibilities, but may want to filter
on those which are true while ignoring all other possiblities.
Examples of these lists could be:
- Things of interest to a user
-- LinkedIn calls these skills, Facebook has 'liked pages', etc
- Movies Watched
-- Netflix surely doesn't (want to) have a USER x MOVIES sized table
-- Nor do they want (user x movies) number of columnfamilies
- Places Visited
-- set yes/no for EVERY location on Earth?
Benchmarks may prove me wrong, but theoretically the performance hit would be
minimal if the data is truly partitioned well, collections are kept small, and
secondary indexing used only as a filter and not data storage.
Dynamic columns may make some of my examples easier, but bring their own
headaches (post-filling dynamically created columns, massively wide tables,
largely unused data == disk bloat).
I'll give a couple examples and use [~jbellis] syntax, as well as a potential
map-based indexing.
- Users contained in group(s):
-- Note: this could be done with columns, but if we assume groups can contain
infinitely many possibilities (like Facebook groups)
- {code:sql}
SELECT * FROM main.users WHERE 'players' IN groups AND 'admins' NOT IN groups;
{code}
- Filter on toggle-based UI elements within user profiles:
{code:sql}
SELECT * FROM main.users WHERE notify['email'] = true;
{code}
Given a possibly endless list, map rows (or data pieces) onto items within that
list:
For instance, user profiles often have 'interests' that could contain
one/multiple of thousands if not millions of possibilities.
Currently, one would have to detail the entirety of the list that has been seen
in one of two ways:
{code:sql}
CREATE TABLE main.interests (
interest_name TEXT PRIMARY KEY,
users LIST TEXT
);
{code}
OR
{code:sql}
CREATE TABLE main.users (
id UUID PRIMARY KEY,
... other user fields ...
interests LIST TEXT
);
{code}
Both of which would require post-result processing (map-reduce or similar) to
find just the users containing a certain key/value.
Rather, with indexing:
{code:sql}
CREATE TABLE main.users (
id UUID PRIMARY KEY,
name TEXT,
age INT,
interests LIST TEXT
);
{code}
where 'interests' is a relatively small (~10-25 elements) list that can be
filtered by:
{code:sql}
SELECT * FROM main.users WHERE 'baseball' IN interests AND 'soccer' IN
interests;
{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
Attachments: 4511.txt
We should allow to 2ndary index on collections. A typical use case would be
to add a 'tag setString' to say a user profile and to query users based on
what tag they have.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[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-tabpanelfocusedCommentId=13825926#comment-13825926 ] Jeremiah Jordan commented on CASSANDRA-4511: I definitely think being able to index the key of a map is useful. There are many times it would have been nice for me to be able to query what rows have this dynamic column, I actually built my own 2i's so I could do that... Since maps are basically one of the big replacements for dynamic columns, I think it would be very useful to index the keys. 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 Attachments: 4511.txt We should allow to 2ndary index on collections. A typical use case would be to add a 'tag setString' to say a user profile and to query users based on what tag they have. -- This message was sent by Atlassian JIRA (v6.1#6144)
[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-tabpanelfocusedCommentId=13825993#comment-13825993 ] Alex Cruise commented on CASSANDRA-4511: FWIW I had a strong use case for indexing both map keys and values. The indexing difficulties (not just in collections) are a big part of the reason I ended up going back to postgres, at least temporarily. :) My data is tagged with customer-supplied arbitrary name/values, and I need to be able to search on both quickly. 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 Attachments: 4511.txt We should allow to 2ndary index on collections. A typical use case would be to add a 'tag setString' to say a user profile and to query users based on what tag they have. -- This message was sent by Atlassian JIRA (v6.1#6144)
[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-tabpanelfocusedCommentId=13824588#comment-13824588
]
Jonathan Ellis commented on CASSANDRA-4511:
---
I'm struggling to think of a use case for indexing map keys. /cc [~pmcfadin]
[~tupshin]
Also, it occurs to me that we don't need to add new syntax if we did this
instead:
{code}
SELECT * FROM myTable WHERE 'awesome' IN tags;
{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
Attachments: 4511.txt
We should allow to 2ndary index on collections. A typical use case would be
to add a 'tag setString' to say a user profile and to query users based on
what tag they have.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[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-tabpanelfocusedCommentId=13602674#comment-13602674 ] Jonathan Ellis commented on CASSANDRA-4511: --- Kind of think we should push this to 2.1. There's a lot of other things I'd rather have in 2.0... 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 Priority: Minor Fix For: 2.0 We should allow to 2ndary index on collections. A typical use case would be to add a 'tag setString' to say a user profile and to query users based on what tag they have. -- 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
