[
https://issues.apache.org/jira/browse/CASSANDRA-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830813#action_12830813
]
Stu Hood edited comment on CASSANDRA-775 at 2/8/10 2:42 AM:
------------------------------------------------------------
> I don't understand the question... using start_key and end_key works like
> "classic" RQ.
Right, but since you don't get Token strings back when you query, you can't
requery using a new Token.
EDIT: Hmm, I guess for the second query you can use a start_key and a
finish_token. Is that the idea?
EDIT2: Actually, that would be invalid with this patch, so the question stands.
was (Author: stuhood):
> I don't understand the question... using start_key and end_key works like
"classic" RQ.
Right, but since you don't get Token strings back when you query, you can't
requery using a new Token.
EDIT: Hmm, I guess for the second query you can use a start_key and a
finish_token. Is that the idea?
> Allow token range queries over Thrift
> -------------------------------------
>
> Key: CASSANDRA-775
> URL: https://issues.apache.org/jira/browse/CASSANDRA-775
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 0.6
>
> Attachments: 775.txt
>
>
> This will allow using Thrift from hadoop jobs, which makes me a little sad
> but MessagingService is just not a good fit for how Hadoop wants to run jobs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
