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 2014/12/15 23:05:13 UTC

[jira] [Resolved] (CASSANDRA-5970) FilteredRangeSlice command for regex searches against column names on known sets of keys

     [ https://issues.apache.org/jira/browse/CASSANDRA-5970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-5970.
---------------------------------------
    Resolution: Duplicate
      Assignee:     (was: Nate McCall)

Opened 8488 as a more general solution.

> FilteredRangeSlice command for regex searches against column names on known sets of keys
> ----------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-5970
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5970
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Nate McCall
>
> This is the ability to apply a regex against columns when the set of keys is known. In filtering the keys, we would like to allow for the following clauses: E, GTE, LTE, NE, inclusive list, exclusive list.
> The end goal is to provide for efficient searching in the case where you have some knowledge of the keys. A specific use case would be, say, searching user agent strings in the given set of date buckets in the classic time-series web log use case. This is a "sweet spot" for Cassandra and providing a more direct method of access for such will help a lot of users.
> Additionally, this will provide some level of feature parity with RDBMS crowd who've had this feature for some time.
> Internally, this will include the introduction of a new Verb, SSTableScanner extension and an ExtendedFilter implementation which applies the regex as well as a new method on StorageProxy.
> This issue does not cover exposing this new query method to thrift and CQL, but obviously that will be required for this to be of any practical use. Those should be covered by separate issues.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)