cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stu Hood (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-1472) Add bitmap secondary indexes
Date Mon, 06 Jun 2011 19:29:59 GMT


Stu Hood commented on CASSANDRA-1472:

By returning the row as a probable match, and resolving using the base data (the brute force
filtering): this is why it is less performant for high update ratios.

With the timestamp work from CASSANDRA-2498, we'd be able to push slightly more down to this
index (especially if we added timestamps to it). If we matched a particular sstable with the
index, and the match has a higher timestamp than any other file, then we can return immediately
with 2498.

> Add bitmap secondary indexes
> ----------------------------
>                 Key: CASSANDRA-1472
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Stu Hood
>            Assignee: Stu Hood
>             Fix For: 1.0
>         Attachments: 0.7-1472-v5.tgz, 0.7-1472-v6.tgz, 0001-CASSANDRA-1472-rebased-to-0.7-branch.txt,
0019-Rename-bugfixes-and-fileclose.txt, 1472-v3.tgz, 1472-v4.tgz, 1472-v5.tgz, anatomy.png,
> Bitmap indexes are a very efficient structure for dealing with immutable data. We can
take advantage of the fact that SSTables are immutable by attaching them directly to SSTables
as a new component (supported by CASSANDRA-1471).

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message