cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7859) Extend freezing to collections
Date Mon, 29 Sep 2014 09:51:34 GMT

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

Sylvain Lebresne commented on CASSANDRA-7859:
---------------------------------------------

bq. By default, indexes on frozen collections will index the entire collection.

What bother me about that is the inconstency with non-frozen collections and I do feel that
this inconsistency will be unintuitive. So I would prefer leaving the default be indexing
by values, and add some new keyword for indexing entire collections. Something like {{CREATE
INDEX ON foo(fullCollection(myMap))}}, excepted that I'm hoping someone can come with a less
crappy name than {{fullCollection}}.

More generally, on the indexing of frozen collections, indexing on the entire collection should
be relatively simple but indexing on values and keys will require new indexes implementation
(new subclasses of {{CompositesIndex}}) and so this should definitively be pushed to a follow-up
ticket imo. Not even sure said ticket should be targeted at 2.1.


> Extend freezing to collections
> ------------------------------
>
>                 Key: CASSANDRA-7859
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7859
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Sylvain Lebresne
>            Assignee: Tyler Hobbs
>             Fix For: 2.1.1
>
>
> This is the follow-up to CASSANDRA-7857, to extend {{frozen}} to collections. This will
allow things like {{map<text, frozen<map<int, int>>>}} for instance, as
well as allowing {{frozen}} collections in PK columns.
> Additionally (and that's alsmot a separate ticket but I figured we can start discussing
it here), we could decide that tuple is a frozen type by default. This means that we would
allow {{tuple<int, text>}} without needing to add {{frozen}}, but we would require {{frozen}}
for complex type inside tuple, so {{tuple<int, list<text>>}} would be rejected,
but not {{tuple<int, frozen<list<text>>>}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message