cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3123) Don't try to build secondary indexes when there is none
Date Fri, 02 Sep 2011 13:24:09 GMT


Jonathan Ellis commented on CASSANDRA-3123:

If we're going to change to relying on the build method to recognize it was asked to perform
a no-op and bail early, we should call it "maybeBuild..." or similar and add javadoc so it's
clear that it might be a no-op.

> Don't try to build secondary indexes when there is none
> -------------------------------------------------------
>                 Key: CASSANDRA-3123
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8.0
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Trivial
>             Fix For: 0.8.5
>         Attachments: 3123.patch
> buildSecondaryIndexes() is sometimes called without checking the cfs has secondary indexes.
Has a result, it prints a useless message and will trigger a bunch of useless action (among
which, a full scan of the indexed column family). This is not a huge problem in 0.8 because
only the fairly new loadNewSSTables() call does this (which doesn't mean we should fix it).
But in trunk, it does this after every streamIn session. 

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


View raw message