[
https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14540714#comment-14540714
]
Jack Krupansky commented on CASSANDRA-6477:
-------------------------------------------
Back to the original description, will the revised MV purpose address the high
cardinality issue? That may depend on what guidance the spec offers for how
data modelers should set up the primary key columns in terms of partition (or
routing!) columns vs. clustering columns.
Is the basic concept that although the selected rows might be scattered across
multiple nodes in the base table, the goal is that they would cluster together
on a single node for the MV table based on careful specification of partition
key columns in the MV?
> Materialized Views (was: 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)
