cassandra-commits mailing list archives

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

    [ https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631459#comment-14631459
] 

T Jake Luciani commented on CASSANDRA-6477:
-------------------------------------------

bq. We'll only if less than a quorum of node don't answer a particular query, which should
be pretty rare unless you have bigger problems with your cluster. 

bq. That said, I hadn't seen we'd decided to go with pairing of base replica to MV replica.

If we replicate to every MV replica from every base replica the write amplification gets much
worse causing more timeouts. So it makes sense to have replication paired.

I do think waiting for the MV updates to be synchronous will cause a lot more timeouts and
write latency (on top of what we have now). But if it's optional then people can choose.

> 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
>
>         Attachments: test-view-data.sh, 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
(v6.3.4#6332)

Mime
View raw message