cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jack Krupansky (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6477) Materialized Views (was: Global Indexes)
Date Fri, 22 May 2015 12:18:21 GMT

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

Jack Krupansky commented on CASSANDRA-6477:
-------------------------------------------

1. Has a decision been made on refresh modes? It sounds like the focus is on "always consistent",
as opposed to manual refresh or one-time without refresh or on some time interval, but is
that simply the default, preferred refresh mode, or the only mode that will be available (initially)?

2. What happens if an MV is created for a base table that is already populated? Will the operation
block while all existing data is propagated to the MV, or will that propagation happen in
the background (in which case, is there a way to monitor its status and completion?), or is
that not supported (initially)?

> 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
>
>
> 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