cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6477) Materialized Views (was: Global Indexes)
Date Thu, 16 Jul 2015 13:58:08 GMT


Sylvain Lebresne commented on CASSANDRA-6477:

bq. The discussion was on how, after a TTL expires and we are persisting null values, it should
be handled.

I'd argue there has been more than one discussion :)

All I want is to make sure we agree the following changes should be made to the patch of this
ticket (if they hasn't been done already):
# lift the limitation of only "a single column that was not part of your original primary
# force users to include _all_ columns from the original PK in the MV PK. In other words,
I agree with Jonathan's remark above that "we shouldn't silently change the definition from
what was given".
# require {{WHERE x IS NOT NULL}} for every column in the MV primary key.

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

View raw message