[
https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Boudreault updated CASSANDRA-6477:
---------------------------------------
Attachment: test-view-data.sh
[~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)
