cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13499) Avoid duplicate calls to the same custom row index
Date Mon, 15 May 2017 12:35:04 GMT


Sam Tunnicliffe commented on CASSANDRA-13499:

I'm not familiar with the Elassandra index implementation(s), but it sounds as if it registers
the same index instance multiple times against separate columns. This is how the DSE Search
& Stratio Lucene implementations used to work, but it is unnecessary now. Since 2.2, it
is possible to register custom indexes that have either zero or multiple target columns. The
decision as to whether a particular update is relevant to the index (i.e. if it contains any
columns which the index cares about) is delegated to the actual index now, through the {{indexerFor}}
method. So I think this patch ought to be unnecessary really as creating a row-based index
should only require a single Index to be registered against the table. 

> Avoid duplicate calls to the same custom row index
> --------------------------------------------------
>                 Key: CASSANDRA-13499
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: vincent royer
>            Priority: Minor
>             Fix For: 3.0.14, 3.11.0, 4.x
>         Attachments: 0006-Avoid-duplicate-calls-to-the-same-custom-index.patch
>   Original Estimate: 2h
>  Remaining Estimate: 2h
> Avoid duplicate calls to the same custom row index by using a dedicated Set<Index>
rather than the collection indexes.values().

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message