[
https://issues.apache.org/jira/browse/CASSANDRA-7859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14149627#comment-14149627
]
Tyler Hobbs commented on CASSANDRA-7859:
----------------------------------------
bq. 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>>>.
I think that's reasonable. There are very few cases where non-frozen tuples
would be useful, let alone the best option, so I don't think we'll ever need
them. It's actually pretty simple to make this change, so I can do that as
part of this ticket.
> 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)
