[
https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348999#comment-14348999
]
Carl Yeksigian commented on CASSANDRA-6477:
-------------------------------------------
bq. Similar conceptually, but much simpler in practice since 8234 envisions
arbitrary joins and subqueries that you need something like hadoop or spark for.
I wanted to get the idea out that this initial implementation will be simpler
and possibly more inefficient because it isn't solving 8234, but that we can
always change later.
I think adding the global index to the schema should be enough for all of the
nodes to insert the values that they have. Either strategy will have some
problems when a replica fails that was supposed to take care of a part of the
range.
> 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)
