[
https://issues.apache.org/jira/browse/CASSANDRA-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712135#action_12712135
]
Jonathan Ellis commented on CASSANDRA-172:
------------------------------------------
thanks, that computeNext is better.
good point on the comparator. i also improved the tests to catch that.
the default UncaughtExceptionHandler will log the exception, so logging it a
second time would be redundant (and logging instead of throwing is bad for
testing).
the comparator bug reminds me that we still have a bug wrt descending queries
from the client's perspective, but I think that can be tackled separately (in
CASSANDRA-196). I'll commit what we have here in the mean time.
> A improved and more general version of get_slice
> ------------------------------------------------
>
> Key: CASSANDRA-172
> URL: https://issues.apache.org/jira/browse/CASSANDRA-172
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Jun Rao
> Assignee: Jun Rao
> Fix For: 0.4
>
> Attachments: 172-addendum-SF.patch, 172-addendum-v2.patch,
> 172-addendum.patch, get_slice_from.patchv1, get_slice_from.patchv2,
> get_slice_from.patchv3
>
>
> Today, get_slice has to scan through all columns in every memtable and
> sstable to get a slice of columns. This becomes inefficient when the number
> of columns in a row is large. We need a more efficient API.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
