[jira] [Updated] (CASSANDRA-10910) Materialized view remained rows

2017-06-22 Thread Jeremy Hanna (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-10910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jeremy Hanna updated CASSANDRA-10910:
-
Component/s: Materialized Views

> Materialized view remained rows
> ---
>
> Key: CASSANDRA-10910
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10910
> Project: Cassandra
>  Issue Type: Bug
>  Components: Coordination, Materialized Views
> 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.4.14#64029)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-10910) Materialized view remained rows

2016-10-24 Thread Carl Yeksigian (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-10910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carl Yeksigian updated CASSANDRA-10910:
---
Component/s: Coordination

> Materialized view remained rows
> ---
>
> Key: CASSANDRA-10910
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10910
> Project: Cassandra
>  Issue Type: Bug
>  Components: Coordination
> 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] [Updated] (CASSANDRA-10910) Materialized view remained rows

2016-01-04 Thread Joshua McKenzie (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-10910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joshua McKenzie updated CASSANDRA-10910:

Reviewer: T Jake Luciani

> 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] [Updated] (CASSANDRA-10910) Materialized view remained rows

2015-12-21 Thread JIRA

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-10910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gábor Auth updated CASSANDRA-10910:
---
Description: 
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)
> 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)
> 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}

It is a bug?

  was:
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)
> 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}

It is a bug?


> 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
>
> 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)
> > update test set key='newKey', value=3 where id='id';
> > select * from test; select * from test_view ;
>  id | key| value
> 

[jira] [Updated] (CASSANDRA-10910) Materialized view remained rows

2015-12-21 Thread JIRA

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-10910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gábor Auth updated CASSANDRA-10910:
---
Description: 
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}

It is a bug?

  was:
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)
> 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)
> 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}

It is a bug?


> 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
>
> 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';

[jira] [Updated] (CASSANDRA-10910) Materialized view remained rows

2015-12-21 Thread JIRA

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-10910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gábor Auth updated CASSANDRA-10910:
---
Description: 
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?

  was:
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}

It is a bug?


> 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
>
> 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...
>