You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/11/20 01:05:20 UTC
[jira] [Resolved] (CASSANDRA-4989) Expose new SliceQueryFilter
features through Thrift interface
[ https://issues.apache.org/jira/browse/CASSANDRA-4989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-4989.
---------------------------------------
Resolution: Won't Fix
Not against this feature on its merits but I don't know anyone who is prioritizing the Thrift API these days. Feel free to reopen if you have a patch.
> 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, 2.0 beta 1
> 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 was sent by Atlassian JIRA
(v6.1#6144)