[jira] [Commented] (CASSANDRA-10910) Materialized view remained rows
[
https://issues.apache.org/jira/browse/CASSANDRA-10910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15154872#comment-15154872
]
Gábor Auth commented on CASSANDRA-10910:
Ok! :)
https://issues.apache.org/jira/browse/CASSANDRA-11198
> 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)
[jira] [Commented] (CASSANDRA-10910) Materialized view remained rows
[
https://issues.apache.org/jira/browse/CASSANDRA-10910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15154865#comment-15154865
]
Gábor Auth commented on CASSANDRA-10910:
I cannot reproduce it from console.
I'm using the cluster through the Datastax Java Driver, the "TRACING ON;" is
the rs.getExecutionInfo() or something else?
> 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)
[jira] [Commented] (CASSANDRA-10910) Materialized view remained rows
[
https://issues.apache.org/jira/browse/CASSANDRA-10910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15154856#comment-15154856
]
Carl Yeksigian commented on CASSANDRA-10910:
Can you try tracing the query and post the result?
{noformat}
TRACING ON;
{noformat}
> 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)
[jira] [Commented] (CASSANDRA-10910) Materialized view remained rows
[
https://issues.apache.org/jira/browse/CASSANDRA-10910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15154787#comment-15154787
]
Gábor Auth commented on CASSANDRA-10910:
"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)
[jira] [Commented] (CASSANDRA-10910) Materialized view remained rows
[
https://issues.apache.org/jira/browse/CASSANDRA-10910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15154760#comment-15154760
]
Carl Yeksigian commented on CASSANDRA-10910:
[~gabor.auth]: what consistency level is this at? Can you do the same query at
a higher CL, or repair the view and see whether the inconsistency persists?
> 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)
[jira] [Commented] (CASSANDRA-10910) Materialized view remained rows
[
https://issues.apache.org/jira/browse/CASSANDRA-10910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15154040#comment-15154040
]
Gábor Auth commented on CASSANDRA-10910:
I've upgraded to datastax-ddc-3.3.0 and... here is a materialized view:
{code}
> DESCRIBE MATERIALIZED VIEW unit_by_transport ;
CREATE MATERIALIZED VIEW unit_by_transport AS
SELECT *
FROM unit
WHERE transportid IS NOT NULL AND type IS NOT NULL
PRIMARY KEY (transportid, id)
WITH CLUSTERING ORDER BY (id ASC)
AND bloom_filter_fp_chance = 0.01
AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
AND comment = ''
AND compaction = {'class':
'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
'max_threshold': '32', 'min_threshold': '4'}
AND compression = {'chunk_length_in_kb': '64', 'class':
'org.apache.cassandra.io.compress.LZ4Compressor'}
AND crc_check_chance = 1.0
AND dclocal_read_repair_chance = 0.1
AND default_time_to_live = 0
AND gc_grace_seconds = 864000
AND max_index_interval = 2048
AND memtable_flush_period_in_ms = 0
AND min_index_interval = 128
AND read_repair_chance = 0.0
AND speculative_retry = '99PERCENTILE';
{code}
I cannot reproduce this but sometimes and somehow happened the same issue:
{code}
> SELECT transportid, id, type FROM unit_by_transport WHERE
> transportid=24f90d20-d61f-11e5-9d3c-8fc3ad6906e2 and
> id=99c05a70-d686-11e5-a169-97287061d5d1;
transportid | id |
type
--+--+--
24f90d20-d61f-11e5-9d3c-8fc3ad6906e2 | 99c05a70-d686-11e5-a169-97287061d5d1 |
null
(1 rows)
> SELECT transportid, id, type FROM unit WHERE
> id=99c05a70-d686-11e5-a169-97287061d5d1;
transportid | id | type
-++--
(0 rows)
{code}
Any idea behind this behavior? :)
> 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)
[jira] [Commented] (CASSANDRA-10910) Materialized view remained rows
[
https://issues.apache.org/jira/browse/CASSANDRA-10910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15092678#comment-15092678
]
Gábor Auth commented on CASSANDRA-10910:
Thank you! What is the planned release date of the 3.0.3 version? :)
> 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)
[jira] [Commented] (CASSANDRA-10910) Materialized view remained rows
[
https://issues.apache.org/jira/browse/CASSANDRA-10910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085720#comment-15085720
]
Carl Yeksigian commented on CASSANDRA-10910:
I've rerun the tests with the latest changes, and the runs look OK, with just
some CI flapping.
> 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.x, 3.x
>
>
> 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)
[jira] [Commented] (CASSANDRA-10910) Materialized view remained rows
[
https://issues.apache.org/jira/browse/CASSANDRA-10910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15085792#comment-15085792
]
T Jake Luciani commented on CASSANDRA-10910:
+1
> 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.x, 3.x
>
>
> 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)
[jira] [Commented] (CASSANDRA-10910) Materialized view remained rows
[
https://issues.apache.org/jira/browse/CASSANDRA-10910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083192#comment-15083192
]
T Jake Luciani commented on CASSANDRA-10910:
The test runs look good, I'm clear on the logic.
I think this comment is wrong though
https://github.com/carlyeks/cassandra/commit/1058108ce8b3a37a60ad312e961687d65d2cc170#diff-599a621b60aab69c0e8946d523743215R304
It says timestamp should use"max but you seem to be fetching the min.
> 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.x, 3.x
>
>
> 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)
[jira] [Commented] (CASSANDRA-10910) Materialized view remained rows
[
https://issues.apache.org/jira/browse/CASSANDRA-10910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083771#comment-15083771
]
Carl Yeksigian commented on CASSANDRA-10910:
Actually, the comment is right, but the ttl and deletion time's were using the
wrong comparators. I've pushed a commit which just changes some of the wording.
When we write the column which is not part of the view's primary key, we use a
timestamp which is further ahead than the view's primary key's timestamp as it
copies the timestamp of the regular column, not the view's primary key. But,
when we generate the timestamp for the tombstone, we currently take the min of
the timestamp of the columns included in the view's primary key, which would
not properly tombstone the value of the other regular column, as it will have
that future timestamp. To fix that, we need to take the max timestamp in order
to generate a tombstone which does cover that regular column's value.
> 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.x, 3.x
>
>
> 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)
[jira] [Commented] (CASSANDRA-10910) Materialized view remained rows
[
https://issues.apache.org/jira/browse/CASSANDRA-10910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15081690#comment-15081690
]
Carl Yeksigian commented on CASSANDRA-10910:
I pushed [a new dtest
branch|https://github.com/carlyeks/cassandra-dtest/tree/10910] which includes a
change to the shadowable tombstone that demonstrates this issue.
> 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.x, 3.x
>
>
> 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)
[jira] [Commented] (CASSANDRA-10910) Materialized view remained rows
[
https://issues.apache.org/jira/browse/CASSANDRA-10910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15081484#comment-15081484
]
T Jake Luciani commented on CASSANDRA-10910:
I'm wondering how this will affect the shadowable tombstone logic. Can you
modify that dtest to include this update?
> 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.x, 3.x
>
>
> 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)
[jira] [Commented] (CASSANDRA-10910) Materialized view remained rows
[
https://issues.apache.org/jira/browse/CASSANDRA-10910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15076084#comment-15076084
]
Gábor Auth commented on CASSANDRA-10910:
Any idea or workaround? :)
> 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
>
> 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)
[jira] [Commented] (CASSANDRA-10910) Materialized view remained rows
[
https://issues.apache.org/jira/browse/CASSANDRA-10910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15067716#comment-15067716
]
Gábor Auth commented on CASSANDRA-10910:
Another test case about the issue:
{code}
> create table test (id text primary key, key text, value int);
> create MATERIALIZED VIEW test_by_key as SELECT * from test where key is not
> null primary key (key, id);
> update test set key='key', value=1 where id='id';
> select * from test; select * from test_by_key ;
id | key | value
+-+---
id | key | 1
(1 rows)
key | id | value
-++---
key | id | 1
(1 rows)
> update test set value=2 where id='id';
> select * from test; select * from test_by_key ;
id | key | value
+-+---
id | key | 2
(1 rows)
key | id | value
-++---
key | id | 2
(1 rows)
> update test set key=null where id='id';
> select * from test; select * from test_by_key ;
id | key | value
+--+---
id | null | 2
(1 rows)
key | id | value
-++---
| id | 2
key | id | 2
(2 rows)
> delete from test where id='id';
> select * from test; select * from test_by_key ;
id | key | value
+-+---
(0 rows)
key | id | value
-++---
| id | 2
key | id | 2
(2 rows)
{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
>
> 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)
[jira] [Commented] (CASSANDRA-10910) Materialized view remained rows
[
https://issues.apache.org/jira/browse/CASSANDRA-10910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066522#comment-15066522
]
Carl Yeksigian commented on CASSANDRA-10910:
I can reproduce this bug on a single machine, so it isn't a latent consistency
issue.
I'll try to diagnose.
> 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
>
> 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)
