cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10910) Materialized view remained rows
Date Tue, 05 Jan 2016 15:06:39 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-10910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)

Mime
View raw message