cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Alves (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-3885) Support multiple ranges in SliceQueryFilter
Date Mon, 04 Jun 2012 18:54:23 GMT


David Alves updated CASSANDRA-3885:

    Attachment: CASSANDRA-3885.patch

Here's a patch that addresses most of the issues:

- A slice range is now specified as a ColumnSlice, a db package immutable object.

- Ranges are passed as arrays and never changed or copied.

The only thing that was not addressed was the cache issue. IMO cache is useful as it prevents
disk rereads. It *might* be better to make sure columns are needed, but even that I'm really
not sure since making sure would require a series of bytebuffer comparisons, and keeping a
single index-lenght (max) of cols is probably not that bad.
> Support multiple ranges in SliceQueryFilter
> -------------------------------------------
>                 Key: CASSANDRA-3885
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: David Alves
>             Fix For: 1.2
>         Attachments: CASSANDRA-3885.patch, CASSANDRA-3885.patch
> This is logically a subtask of CASSANDRA-2710, but Jira doesn't allow sub-sub-tasks.
> We need to support multiple ranges in a SliceQueryFilter, and we want querying them to
be efficient, i.e., one pass through the row to get all of the ranges, rather than one pass
per range.
> Supercolumns are irrelevant since the goal is to replace them anyway.  Ignore supercolumn-related
code or rip it out, whichever is easier.
> This is ONLY dealing with the storage engine part, not the StorageProxy and Command intra-node
messages or the Thrift or CQL client APIs.  Thus, a unit test should be added to ColumnFamilyStoreTest
to demonstrate that it works.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message