[
https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14380504#comment-14380504
]
Carl Yeksigian commented on CASSANDRA-6477:
-------------------------------------------
I've pushed up a few updates to the branch. There was an issue with clustering
columns which [~philipthompson] pointed out, which has been resolved; an index
on a clustering column works properly now.
Currently, {{ALLOW FILTERING}} queries are disallowed. We can change that
behavior later, but it should be a follow-on ticket. Also disabled ins any
index including Collections, either as target or an included column. This
should also be added, but it will require a substantial rewrite, and makes
sense to hold off on until the major rewrite after CASSANDRA-8099.
[~pateljay3001]: I think it makes sense to wait until this gets committed.
Especially with the storage engine refactor, there may come significant changes
to the global indexes, so any work would need to be redone later.
It currently doesn't have any sort of read-repair because it doesn't work at
the level of mutation applications. It also doesn't have a proper repair built
in; we can use the {{Builder}} from the creation part to add a rebuild, but we
would have to drop the data currently stored to make sure we aren't returning
previous results.
> Global indexes
> --------------
>
> Key: CASSANDRA-6477
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6477
> Project: Cassandra
> Issue Type: New Feature
> Components: API, Core
> Reporter: Jonathan Ellis
> Assignee: Carl Yeksigian
> Labels: cql
> Fix For: 3.0
>
>
> Local indexes are suitable for low-cardinality data, where spreading the
> index across the cluster is a Good Thing. However, for high-cardinality
> data, local indexes require querying most nodes in the cluster even if only a
> handful of rows is returned.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
