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 Fri, 17 Jul 2015 18:33:14 GMT


Sylvain Lebresne commented on CASSANDRA-6477:

The batchlog is to guarantee eventual consistency of the MV. The user CL is mostly to get
guarantee that you can see your writes. I don't understand why you'd think the former would
prevent the latter.

But anyway, I'll retract part of my previous comment. I'm not really that oppose to having
the option of doing asynchronous MV update. Rather I feel that 1) doing synchonous updates
(which is equivalent of respecting the CL for the MV update too) should be the default because
that's what people will expect (as exemplified by Jon and Brian response above) and 2) that
we should discuss the addition of such option in a followup ticket. The reason for the later
is that I think there is multiple ways to do this, and I typically don't like the idea of
making a table option at all, so I don't see the point of discussing this here.

> 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