[
https://issues.apache.org/jira/browse/CASSANDRA-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12704196#action_12704196
]
Jonathan Ellis commented on CASSANDRA-71:
-----------------------------------------
1. ok
2. ok
3. because the deletion-check code is very very expensive. we shouldn't allow
get_key_range to DOS ourselves. you are right that this should be a parameter.
4. No, I think you had it right earlier in CASSANDRA-65 that since the iterator
alters the FS state, FS should implement iterator rather than being separate.
5. seekTo does the checking, or am I missing something?
6. we can catch once in forward or twice in next and hasNext; we can't throw
farther b/c the iterator interface does not allow it. IMO catching once is the
lesser evil here.
7. new system tests are added. I am not a fan of covering in unit tests what
is covered by system tests, other things being equal.
> Range query support
> -------------------
>
> Key: CASSANDRA-71
> URL: https://issues.apache.org/jira/browse/CASSANDRA-71
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Fix For: 0.3
>
> Attachments: 71.patch
>
>
> Scan for keys by range (between X and Y) or prefix (starting with P).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
