[jira] [Commented] (CASSANDRA-9196) Do not rebuild indexes if no columns are actually indexed

["Jeremiah Jordan (JIRA)" <ji...@apache.org>]

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

Jeremiah Jordan commented on CASSANDRA-9196:
--------------------------------------------

This looks like it may be broken for indexes on DynamicCompositeType columns.  Still looking into it, but thought I would post a heads up.

> Do not rebuild indexes if no columns are actually indexed
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-9196
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9196
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Sergio Bossa
>            Assignee: Sergio Bossa
>             Fix For: 2.0.15, 2.1.5
>
>         Attachments: 2.0-CASSANDRA-9196.txt, 2.1-CASSANDRA-9196.txt
>
>
> When rebuilding secondary indexes, the index task is executed regardless if the actual {{SecondaryIndex#indexes(ByteBuffer )}} implementation of any index returns true for any column, meaning that the expensive task of going through all sstables and related rows will be executed even if in the end no column/row will be actually indexed.
> This is a huge performance hit when i.e. bootstrapping with large datasets on tables having custom secondary index implementations whose {{indexes()}} implementation might return false.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)