cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suhail Doshi (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-570) Pattern matching / better filtering for column / super column names for get_slice
Date Mon, 23 Nov 2009 01:47:39 GMT


Suhail Doshi commented on CASSANDRA-570:

Is it possible to improve slicing in the following way then:

Ability to slice a column and specify an exact super column key, for example:

column_1 {
   sc1: {}

column_2 {
   sc1: {}
   sc2: {}

Be able to slice by "column_1" to "column_2" but instead of grabbing every column, grab only
super column "sc1" from each? The reasoning is that it's terrible to have to slice by column
and get *every* super column and have it held in memory for the client application.

> Pattern matching / better filtering for column / super column names for get_slice
> ---------------------------------------------------------------------------------
>                 Key: CASSANDRA-570
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>    Affects Versions: 0.5, 0.9
>            Reporter: Suhail Doshi
> It would be useful to be able to pattern match or wildcard in a column name. The problem
is sometimes you need more depth where supercolumns are not enough. The hack around solution
is prefixing things but when you prefix things you realize you need a better way to filter
through the prefixed data.
> I am voting for a way to pattern match or permit some kind of wildcarding in the column
if possible.
> For example:
> column name="prefix_20091122_male"
> column name="prefix2_20091122_female"
> Cassandra could be used in complex data situation for people who want to grab all data
from the date: 20091122 or grab all data from the date: "20091122" and that is of type male
or female through some kind of wildcard / pattern matching scheme.
> I won't propose one because I do not understand Cassandra well enough to but it seems
like this may be possible and worth a discussion.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message