[
https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534400#comment-14534400
]
Sylvain Lebresne commented on CASSANDRA-6477:
---------------------------------------------
bq. I'm warming up to the idea of calling it MV but only IF we're committed to
fleshing it out to match SELECT.
+1. On top of having a clear path for added flexibility, having the underlying
table being directly exposed make it clear that you can only access what you
denormalize (this is obvious for MV, less with a GI) and simplify the read path
(the CQL parts of the read path).
> 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.x
>
>
> 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)
