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

Sylvain Lebresne commented on CASSANDRA-4989:
---------------------------------------------

I'm not sure I understand your example. The way I understand your {{Query slice 
range (t1,) group by prefix (1) limit (1)}} you are literally asking for every 
columns staring with t1. You can absolutely do that with the thrift API 
currently (using CompositeType has a end-of-component feature).

Besides, the group by prefix is a CQL3 implementation detail and does more than 
just grouping by prefix when counting (it also skip deleted records in some 
conditions that only make sense for CQL3 for instance). The exact semantic of 
that counting may change depending on the needs of CQL3 and is not something 
that has ever been meant to be exposed directly. 
                
> Expose new SliceQueryFilter features through Thrift interface
> -------------------------------------------------------------
>
>                 Key: CASSANDRA-4989
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4989
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: API
>    Affects Versions: 1.2.0, 1.2.1, 1.3
>            Reporter: Cristian Opris
>
> SliceQueryFilter has some very useful new features like ability to specify a 
> composite column prefix to group by and specify a limit of groups to return.
> This is very useful if for example I have a wide row with columns prefixed by 
> timestamp and I want to retrieve the latest columns, but I don't know the 
> column names. Say I have a row
> {{row -> (t1, c1), (t1, c2)... (t1, cn) ... (t0,c1) ... etc}}
> Query slice range (t1,) group by prefix (1) limit (1)
> As a more general question, is the Thrift interface going to be kept 
> up-to-date with the feature changes or will it be left behind (a mistake IMO) 
> ?

--
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

Reply via email to