cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6477) Materialized Views (was: Global Indexes)
Date Fri, 17 Jul 2015 15:59:13 GMT


T Jake Luciani commented on CASSANDRA-6477:

bq. Frankly, I'm pretty negative on adding such option. 

But then why do we even offer the batchlog at all?  Hand rolled materialized views use them.
 And if you feel we should guarantee a consistency level then you would never use a batchlog.
Since any timeout would mean you didn't achieve your consistency level and you must retry.

If you are talking about just the UE then we could check the MV replica UP/Down status in
the coordinator as well as the base.

> 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