cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ahmet AKYOL (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5313) provide a cardinality function for collection types ( CQL3 )
Date Tue, 05 Mar 2013 18:24:13 GMT


Ahmet AKYOL commented on CASSANDRA-5313:

{quote} but there is always the worry that people will expect it to be smarter than that when
it isn't {quote} 
that's why I told my wish "maybe mixing counter columns and other data types in a table could
be better ". I also said "from schema design point of view" because I didn't figure how to
design my use case yet.Perhaps, it's time for you (guys) to write a "Cassandra in action"
book since cql 3 is a bit [mystery even for experts|].
I assure you, I'll be the first one to buy it in [MEAP|]

Anyway, maybe this feature still can be useful for lazy loading. what I mean is, we can only
store keys of another table in a set for uniqueness and still query the count (cardinality)
in cql without any trick. 
> provide a cardinality function for collection types ( CQL3 )
> ------------------------------------------------------------
>                 Key: CASSANDRA-5313
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Ahmet AKYOL
>              Labels: cql3, ponies
> Currently , cql3 doesn't provide a cardinality function for collection types. It'll be
great to have one:
> {code}
> select content, cardinality(like_set),cardinality(dislike_set) from comments where id=?;
> {code}
> or size as keyword
> {code}
> select content, size(like_set),size(dislike_set) from comments where id=?;
> {code}
> Something similar in SQL is [cardinality of nested tables|]

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:

View raw message