You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Suhail Doshi (JIRA)" <ji...@apache.org> on 2009/11/23 01:55:39 UTC
[jira] Created: (CASSANDRA-570) Pattern matching / better filtering
for column / super column names for get_slice
Pattern matching / better filtering for column / super column names for get_slice
---------------------------------------------------------------------------------
Key: CASSANDRA-570
URL: https://issues.apache.org/jira/browse/CASSANDRA-570
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.
[jira] Commented: (CASSANDRA-570) Pattern matching / better
filtering for column / super column names for get_slice
Posted by "Suhail Doshi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781270#action_12781270 ]
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: https://issues.apache.org/jira/browse/CASSANDRA-570
> 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.
[jira] Resolved: (CASSANDRA-570) Pattern matching / better
filtering for column / super column names for get_slice
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-570.
--------------------------------------
Resolution: Won't Fix
> Pattern matching / better filtering for column / super column names for get_slice
> ---------------------------------------------------------------------------------
>
> Key: CASSANDRA-570
> URL: https://issues.apache.org/jira/browse/CASSANDRA-570
> 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.
[jira] Resolved: (CASSANDRA-570) Pattern matching / better
filtering for column / super column names for get_slice
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-570.
--------------------------------------
Resolution: Fixed
Slicing works because data in a row is stored ordered by its Comparator. So a slice is "seek to the closest column not greater than the start, and read until you hit the finish, or count." More complex operations cannot be done efficiently, and should be done client side if they are done at all.
> Pattern matching / better filtering for column / super column names for get_slice
> ---------------------------------------------------------------------------------
>
> Key: CASSANDRA-570
> URL: https://issues.apache.org/jira/browse/CASSANDRA-570
> 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.
[jira] Commented: (CASSANDRA-570) Pattern matching / better
filtering for column / super column names for get_slice
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781272#action_12781272 ]
Jonathan Ellis commented on CASSANDRA-570:
------------------------------------------
That would be fine, although it would require subcolumn indexing to really be useful.
> Pattern matching / better filtering for column / super column names for get_slice
> ---------------------------------------------------------------------------------
>
> Key: CASSANDRA-570
> URL: https://issues.apache.org/jira/browse/CASSANDRA-570
> 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.
[jira] Reopened: (CASSANDRA-570) Pattern matching / better
filtering for column / super column names for get_slice
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis reopened CASSANDRA-570:
--------------------------------------
> Pattern matching / better filtering for column / super column names for get_slice
> ---------------------------------------------------------------------------------
>
> Key: CASSANDRA-570
> URL: https://issues.apache.org/jira/browse/CASSANDRA-570
> 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.
[jira] Commented: (CASSANDRA-570) Pattern matching / better
filtering for column / super column names for get_slice
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781276#action_12781276 ]
Jonathan Ellis commented on CASSANDRA-570:
------------------------------------------
(CASSANDRA-571)
> Pattern matching / better filtering for column / super column names for get_slice
> ---------------------------------------------------------------------------------
>
> Key: CASSANDRA-570
> URL: https://issues.apache.org/jira/browse/CASSANDRA-570
> 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.