[
https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14553176#comment-14553176
]
Carl Yeksigian commented on CASSANDRA-6477:
-------------------------------------------
Pushed a [new branch|https://github.com/carlyeks/cassandra/tree/ticket/6477-3]
which includes the materialized view syntax [~jbellis] proposed:
{code}
CREATE MATERIALIZED VIEW users_by_age AS
SELECT age, user_id, x, y, z FROM users
PRIMARY KEY (age, user_id)
{code}
The branch also includes the consistency updates proposed earlier in this
ticket, as well as initial support for collection.
Main outstanding issues:
- When overloaded with inserts to a single partition key in the base,
tombstones aren't always properly generated for the view; this inconsistency
doesn't get corrected with more time since repair doesn't check view versus base
- An insert to a collection produces a range tombstone which isn't translated
properly against the view; only range tombstones covering the whole row are
handled
> 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 beta 1
>
>
> 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)
