cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3647) Support set and map value types in CQL
Date Tue, 12 Jun 2012 12:22:44 GMT


Jonathan Ellis commented on CASSANDRA-3647:

bq. users can't implement discard as well as we can 

I'd argue that if you cared more about the value than the ordering, you should be using a
Set instead.  And our Sets are inherently ordered (by value), which obviates one of the reasons
to use a List when you really mean a Set in many languages.

bq. I'm not sure I'm convinced by that syntax for sets, as this reuse a very standard notation
for something not standard at all

I'm not sure I follow, what else would S[4] mean?  That is: I'm okay with being non-standard,
as long as it's not ambiguous.

bq. some syntax that were proposed seemed to be a problem for hive

Good point, let's see what Jake says.
> Support set and map value types in CQL
> --------------------------------------
>                 Key: CASSANDRA-3647
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API, Core
>            Reporter: Jonathan Ellis
>            Assignee: Sylvain Lebresne
>              Labels: cql
>             Fix For: 1.2
> Composite columns introduce the ability to have arbitrarily nested data in a Cassandra
row.  We should expose this through CQL.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message