cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Edmonds (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-855) easier prefix searching with get_range_slices
Date Sat, 06 Mar 2010 01:09:27 GMT

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

Robert Edmonds updated CASSANDRA-855:
-------------------------------------

    Description: 
it would be nice if there were a SlicePredicate which could perform prefix searching with
get_range_slices.

e.g., if keys "foo", "bar", "baz", "quux" are present, retrieve only the keys starting with
"ba". this is currently possible by using a SliceRange predicate with start="ba" and finish="bb",
but calculating the next lowest key after the prefix isn't necessarily trivial.

  was:
it would be nice if there were a SlicePredicate which could perform prefix searching.

it would be nice if there were an easier way to perform prefix searches with get_range_slices.

e.g., if keys "foo", "bar", "baz", "quux" are present, retrieve only the keys starting with
"ba". this is currently possible by using a SliceRange predicate with start="ba" and finish="bb",
but calculating the next lowest key after the prefix isn't necessarily trivial.


> easier prefix searching with get_range_slices
> ---------------------------------------------
>
>                 Key: CASSANDRA-855
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-855
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Robert Edmonds
>            Priority: Minor
>
> it would be nice if there were a SlicePredicate which could perform prefix searching
with get_range_slices.
> e.g., if keys "foo", "bar", "baz", "quux" are present, retrieve only the keys starting
with "ba". this is currently possible by using a SliceRange predicate with start="ba" and
finish="bb", but calculating the next lowest key after the prefix isn't necessarily trivial.

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


Mime
View raw message