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] Updated: (CASSANDRA-172) A improved and more general version of get_slice
Date Tue, 19 May 2009 15:32:45 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jun Rao updated CASSANDRA-172:
------------------------------

    Attachment: get_slice_from.patchv3

Attach patch v3.  Avoided calling CF.resolve. Took out offset from api. Changed coding style
in a few places. Renamed ColumnSliceBlockReader to ColumnGroupReader.

Regarding the issue of including an offset in the API. Is your main concern that the api becomes
less clear? The code complexity to support offset is minimal.

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


Mime
View raw message