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] [Comment Edited] (CASSANDRA-6477) Materialized Views (was: Global Indexes)
Date Fri, 24 Jul 2015 16:17:09 GMT

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

T Jake Luciani edited comment on CASSANDRA-6477 at 7/24/15 4:17 PM:
--------------------------------------------------------------------

bq. We could also do with some comments around things like

Yeah I've split it out to two methods locally.

bq. OK, so we have deadlock in that case.

How do secondary index updates work then? We take a write oporder for another table inside
the base table update.


was (Author: tjake):
bq. We could also do with some comments around things like

Yeah I've split it out to two methods locally.

bq. OK, so we have deadlock in that case.

How do secondary index updates work then? We take a write oporder for another table inside
the base table update?

> 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