[
https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14540699#comment-14540699
]
Jack Krupansky commented on CASSANDRA-6477:
-------------------------------------------
Is it fair to say that the primary technique for using this feature is to have
one base table and n views of that table, each with a different selection of
the base columns as the primary key of the view, with all rows selected,
possibly projected differently but with different keys?
Would it also be sensible to select a subset of rows? Although that might
confuse some users who might think it would give them sophisticated ad hoc
queries when in fact the query column values are fixed. For example, select all
rows for a specific state. In this way, it doesn't offer what a global index
would offer.
> 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)
