cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl Yeksigian (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6477) Materialized Views (was: Global Indexes)
Date Wed, 20 May 2015 21:40:06 GMT


Carl Yeksigian commented on CASSANDRA-6477:

Pushed a [new branch|] which includes
the materialized view syntax [~jbellis] proposed:

SELECT age, user_id, x, y, z FROM users
PRIMARY KEY (age, user_id)

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:
>             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

View raw message