cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1615) cli index scan support
Date Wed, 20 Oct 2010 03:31:36 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922837#action_12922837
] 

Jonathan Ellis commented on CASSANDRA-1615:
-------------------------------------------

1) say you want to get the first 100 users born in 1980.  then you want to get the next 100.
 for the second call you would pass as start_key the last row key you got back from the first
call.  generally the first call start_key will always be empty.

2) CLI does not have sophisticated SlicePredicate anywhere else so adding it here is not required.
 Fetching the whole row is fine.

We should have LIMIT support like in the list command or equivalent, defaulting to something
sane like 100.

> cli index scan support
> ----------------------
>
>                 Key: CASSANDRA-1615
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1615
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Tools
>    Affects Versions: 0.7 beta 1
>            Reporter: Jonathan Ellis
>            Assignee: Pavel Yaskevich
>             Fix For: 0.7.0
>
>
> cli needs to support get_indexed_slices.
> one syntax might be
> {code}
> GET cf WHERE column1=value1 AND column2>value2
> {code}
> (OR is not supported by get_indexed_slices, only AND)

-- 
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