[jira] [Created] (CASSANDRA-6914) Map element is not allowed in CAS condition with DELETE/UPDATE query
Dmitriy Ukhlov created CASSANDRA-6914:
-
Summary: Map element is not allowed in CAS condition with
DELETE/UPDATE query
Key: CASSANDRA-6914
URL: https://issues.apache.org/jira/browse/CASSANDRA-6914
Project: Cassandra
Issue Type: Bug
Reporter: Dmitriy Ukhlov
CREATE TABLE test (id int, data map, PRIMARY KEY(id));
INSERT INTO test (id, data) VALUES (1,{'a':'1'});
DELETE FROM test WHERE id=1 IF data['a']=null;
Bad Request: line 1:40 missing EOF at '='
UPDATE test SET data['b']='2' WHERE id=1 IF data['a']='1';
Bad Request: line 1:53 missing EOF at '='
These queries was successfuly executed with cassandra 2.0.5, but don't work in
2.0.6 release
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CASSANDRA-6429) CQL3 SELECT improvements for collections
[ https://issues.apache.org/jira/browse/CASSANDRA-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Ukhlov updated CASSANDRA-6429: -- Description: I have found proposal for improvement there: https://issues.apache.org/jira/browse/CASSANDRA-3647 It is proposed to make next improvement: SELECT L[1] FROM ...; -- select list element by index SELECT M["foo"] FROM ...; -- select specific map elements SELECT S["a":"z"] FROM ...; -- select a slice of a set (since after all our sets and maps are sorted) But I couldn't find corresponding ticket for it. was: I have found proposal for improvement there: https://issues.apache.org/jira/browse/CASSANDRA-3647 It is proposed to make next improvement: SELECT L[1] FROM ...; -- select list element by index SELECT M["foo"] FROM ...; -- select specific map elements SELECT S["a":"z"] FROM ...; -- select a slice of a set (since after all our sets and maps are sorted) But I couldn't find corresponded ticket for it. > CQL3 SELECT improvements for collections > > > Key: CASSANDRA-6429 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6429 > Project: Cassandra > Issue Type: Improvement >Reporter: Dmitriy Ukhlov > > I have found proposal for improvement there: > https://issues.apache.org/jira/browse/CASSANDRA-3647 > It is proposed to make next improvement: > SELECT L[1] FROM ...; -- select list element by index > SELECT M["foo"] FROM ...; -- select specific map elements > SELECT S["a":"z"] FROM ...; -- select a slice of a set (since after all our > sets and maps are sorted) > But I couldn't find corresponding ticket for it. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CASSANDRA-6429) CQL3 SELECT improvements for collections
[ https://issues.apache.org/jira/browse/CASSANDRA-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Ukhlov updated CASSANDRA-6429: -- Since Version: (was: 2.0.2) > CQL3 SELECT improvements for collections > > > Key: CASSANDRA-6429 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6429 > Project: Cassandra > Issue Type: Improvement >Reporter: Dmitriy Ukhlov > > I have found proposal for improvement there: > https://issues.apache.org/jira/browse/CASSANDRA-3647 > It is proposed to make next improvement: > SELECT L[1] FROM ...; -- select list element by index > SELECT M["foo"] FROM ...; -- select specific map elements > SELECT S["a":"z"] FROM ...; -- select a slice of a set (since after all our > sets and maps are sorted) > But I couldn't find corresponded ticket for it. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CASSANDRA-6430) DELETE with IF = clause doesn't work properly if more then one row are going to be deleted
Dmitriy Ukhlov created CASSANDRA-6430: - Summary: DELETE with IF = clause doesn't work properly if more then one row are going to be deleted Key: CASSANDRA-6430 URL: https://issues.apache.org/jira/browse/CASSANDRA-6430 Project: Cassandra Issue Type: Bug Reporter: Dmitriy Ukhlov CREATE TABLE test(key int, sub_key int, value text, PRIMARY KEY(key, sub_key) ); INSERT INTO test(key, sub_key, value) VALUES(1,1, '1.1'); INSERT INTO test(key, sub_key, value) VALUES(1,2, '1.2'); INSERT INTO test(key, sub_key, value) VALUES(1,3, '1.3'); SELECT * from test; key | sub_key | value -+-+--- 1 | 1 | 1.1 1 | 2 | 1.2 1 | 3 | 1.3 DELETE FROM test WHERE key=1 IF value='1.2'; [applied] --- False <=== I guess second row should be removed SELECT * from test; key | sub_key | value -+-+--- 1 | 1 | 1.1 1 | 2 | 1.2 1 | 3 | 1.3 (3 rows) DELETE FROM test WHERE key=1; SELECT * from test; (0 rows) <=== all rows were removed: OK -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (CASSANDRA-6429) CQL3 SELECT improvements for collections
Dmitriy Ukhlov created CASSANDRA-6429: - Summary: CQL3 SELECT improvements for collections Key: CASSANDRA-6429 URL: https://issues.apache.org/jira/browse/CASSANDRA-6429 Project: Cassandra Issue Type: Improvement Reporter: Dmitriy Ukhlov I have found proposal for improvement there: https://issues.apache.org/jira/browse/CASSANDRA-3647 It is proposed to make next improvement: SELECT L[1] FROM ...; -- select list element by index SELECT M["foo"] FROM ...; -- select specific map elements SELECT S["a":"z"] FROM ...; -- select a slice of a set (since after all our sets and maps are sorted) But I couldn't find corresponded ticket for it. -- This message was sent by Atlassian JIRA (v6.1#6144)
