[
https://issues.apache.org/jira/browse/CASSANDRA-10910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15154787#comment-15154787
]
Gábor Auth edited comment on CASSANDRA-10910 at 2/19/16 8:28 PM:
-----------------------------------------------------------------
"Consistency level set to ALL."
It was the highest CL... :(
How can I repair the materialized view? I've started a full repair now:
{code}
[2016-02-19 20:03:45,096] Starting repair command #211, repairing keyspace
test20160215 with repair options (parallelism: parallel, primary range: false,
incremental: false, job threads: 1, ColumnFamilies: [], dataCenters: [], hosts:
[], # of ranges: 216)
{code}
Finished:
{code}
> /home/cassandra/datastax-ddc-3.3.0/bin/nodetool repair -full test20160215
[...]
[2016-02-19 20:26:32,057] Repair command #1 finished in 4 minutes 46 seconds
{code}
Same issue with ALL consistency level... :(
was (Author: gabor.auth):
"Consistency level set to ALL."
It was the highest CL... :(
How can I repair the materialized view? I've started a full repair now:
{code}
[2016-02-19 20:03:45,096] Starting repair command #211, repairing keyspace
test20160215 with repair options (parallelism: parallel, primary range: false,
incremental: false, job threads: 1, ColumnFamilies: [], dataCenters: [], hosts:
[], # of ranges: 216)
{code}
> Materialized view remained rows
> -------------------------------
>
> Key: CASSANDRA-10910
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10910
> Project: Cassandra
> Issue Type: Bug
> Environment: Cassandra 3.0.0
> Reporter: Gábor Auth
> Assignee: Carl Yeksigian
> Fix For: 3.0.3, 3.3
>
>
> I've created a table and a materialized view.
> {code}
> > CREATE TABLE test (id text PRIMARY KEY, key text, value int);
> > CREATE MATERIALIZED VIEW test_view AS SELECT * FROM test WHERE key IS NOT
> > NULL PRIMARY KEY(key, id);
> {code}
> I've put a value into the table:
> {code}
> > update test set key='key', value=1 where id='id';
> > select * from test; select * from test_view ;
> id | key | value
> ----+-----+-------
> id | key | 1
> (1 rows)
> key | id | value
> -----+----+-------
> key | id | 1
> (1 rows)
> {code}
> I've updated the value without specified the key of the materialized view:
> {code}
> > update test set value=2 where id='id';
> > select * from test; select * from test_view ;
> id | key | value
> ----+-----+-------
> id | key | 2
> (1 rows)
> key | id | value
> -----+----+-------
> key | id | 2
> (1 rows)
> {code}
> It works as I think...
> ...but I've updated the key of the materialized view:
> {code}
> > update test set key='newKey' where id='id';
> > select * from test; select * from test_view ;
> id | key | value
> ----+--------+-------
> id | newKey | 2
> (1 rows)
> key | id | value
> --------+----+-------
> key | id | 2
> newKey | id | 2
> (2 rows)
> {code}
> ...I've updated the value of the row:
> {code}
> > update test set key='newKey', value=3 where id='id';
> > select * from test; select * from test_view ;
> id | key | value
> ----+--------+-------
> id | newKey | 3
> (1 rows)
> key | id | value
> --------+----+-------
> key | id | 2
> newKey | id | 3
> (2 rows)
> {code}
> ...I've deleted the row by the id key:
> {code}
> > delete from test where id='id';
> > select * from test; select * from test_view ;
> id | key | value
> ----+-----+-------
> (0 rows)
> key | id | value
> -----+----+-------
> key | id | 2
> (1 rows)
> {code}
> Is it a bug?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
