[
https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14646523#comment-14646523
]
Aleksey Yeschenko commented on CASSANDRA-6477:
----------------------------------------------
Nits:
per convention, {{MATERIALIZEDVIEWS}} should be {{MATERIALIZED_VIEWS}},
likewise {{"materializeviews"}} -> {{"materiazlized_views"}} (schema keyspace
table name).
{{MaterializedViews}} table def in {{SchemaKeyspace}} is all messed up,
alignment-wise (and {{columnfamily_name}} must be {{table_name}}, even though
we'll be reworking that whole table for the beta).
The {{materializedViews}} map in {{CFMetaData}} is a regular {{HashMap}} and
it's being updated in place. It will occasionally cause
{{ConcurrentModificationException}}. The whole thing should be made immutable
like {{Triggers}}, as {{CFMetaData}} will be so entirely, soon.
> 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.0 alpha 1
>
> Attachments: test-view-data.sh, users.yaml
>
>
> 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)
