cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jun Rao (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-172) A improved and more general version of get_slice
Date Mon, 18 May 2009 21:05:45 GMT

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

Jun Rao commented on CASSANDRA-172:
-----------------------------------

For the CF wrapper, I need to resolve a column at a time so that I know when I have enough
columns to return (since a column could be deleted). I am not exactly sure how to apply your
addColumn suggestion, since there is no place to call a single final resolve.

If all iterators are empty, an empty CF will be returned. I don't really need to update the
tombstone in the CF unless for read-repair considerations. However, the current read-repair
logic doesn't deal with CF removal.


> 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: get_slice_from.patchv1, get_slice_from.patchv2
>
>
> 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.


Mime
View raw message