[
https://issues.apache.org/jira/browse/CASSANDRA-5970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756339#comment-13756339
]
Jonathan Ellis commented on CASSANDRA-5970:
-------------------------------------------
It sounds like you have some code already, but ISTM it would be most
straightforward to implement this as a predicate to the existing slice verb.
Or put another way, making the slice code a closer match to the range
(sequential scan) code that already has a concept of predicates being queried.
> 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 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
