Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 168DB1883D for ; Wed, 1 Jul 2015 19:47:09 +0000 (UTC) Received: (qmail 90678 invoked by uid 500); 1 Jul 2015 19:47:09 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 90648 invoked by uid 500); 1 Jul 2015 19:47:08 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 90635 invoked by uid 99); 1 Jul 2015 19:47:08 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2015 19:47:08 +0000 Date: Wed, 1 Jul 2015 19:47:08 +0000 (UTC) From: "Alan Boudreault (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (CASSANDRA-6477) Materialized Views (was: Global Indexes) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14610902#comment-14610902 ] Alan Boudreault edited comment on CASSANDRA-6477 at 7/1/15 7:47 PM: -------------------------------------------------------------------- [~carlyeks] Here is a small script to reproduce the issue discussed on hipchat: [^test-view-data.sh] . Give a try to that script and let me know if you can also reproduce the issue. It is possible that you have to run the script 2-3 times before. I noticed that sometime, the count is OK. For the record, the issue is that my materialized view is not synchronized properly with the data in my main table. There is no hints or batchlog recorded. Output of the issue: {code} MAIN TABLE COUNT Consistency level set to ALL. count ------- 8 (1 rows) MV TABLE COUNT - node1 Consistency level set to ALL. count ------- 7 (1 rows) \MAIN TABLE DATA Consistency level set to ALL. id | v ----+--- 5 | 5 1 | 1 8 | 8 2 | 2 4 | 4 7 | 7 6 | 6 3 | 3 (8 rows) MV TABLE DATA Consistency level set to ALL. v | id ---+---- 1 | 1 8 | 8 2 | 2 4 | 4 7 | 7 6 | 6 3 | 3 (7 rows) {code} was (Author: aboudreault): [~carlyeks] Here is a small script to reproduce the issue discussed on hipchat: [^test-view.data.sh] . Give a try to that script and let me know if you can also reproduce the issue. It is possible that you have to run the script 2-3 times before. I noticed that sometime, the count is OK. For the record, the issue is that my materialized view is not synchronized properly with the data in my main table. There is no hints or batchlog recorded. Output of the issue: {code} MAIN TABLE COUNT Consistency level set to ALL. count ------- 8 (1 rows) MV TABLE COUNT - node1 Consistency level set to ALL. count ------- 7 (1 rows) \MAIN TABLE DATA Consistency level set to ALL. id | v ----+--- 5 | 5 1 | 1 8 | 8 2 | 2 4 | 4 7 | 7 6 | 6 3 | 3 (8 rows) MV TABLE DATA Consistency level set to ALL. v | id ---+---- 1 | 1 8 | 8 2 | 2 4 | 4 7 | 7 6 | 6 3 | 3 (7 rows) {code} > 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 > > > 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)