[ https://issues.apache.org/jira/browse/CASSANDRA-10264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14955163#comment-14955163 ]
Sylvain Lebresne commented on CASSANDRA-10264: ---------------------------------------------- bq. {{IF x = 3}} was previously working even if the regular expression was wrong. I don't understand how cqlsh works. The fact is, the value of {{<conditioncmp>}} in your patch seems to only matter for {{!=}}. That is, if you set {{<conditioncmp> ::= /\!=/ ;}} then all condition are still working (being it {{=}}, {{>}}, {{<}}, {{>=}} or {{<=}}) (and by "working", I mean that the statements aren't rejected by cqlsh. Actual completion seems to be broken by that {{<conditioncmp>}} change, which I can live with). Besides, that still begs the question: what was wrong with the original version and why do we need this change? I'm good with the rest of the CQL change, but I'm mystified by the cqlsh part and I'm not very comfortable +1ing something that doesn't make sense to me. [~thobbs] [~Stefania] you both have experience with cqlsh, can any of you shed some light on this? > Unable to use conditions on static columns for DELETE > ----------------------------------------------------- > > Key: CASSANDRA-10264 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10264 > Project: Cassandra > Issue Type: Bug > Components: Core > Environment: Cassandra 2.2.0 > Reporter: DOAN DuyHai > Assignee: Benjamin Lerer > Attachments: 10264-2.1.txt, 10264-3.0.txt > > > {noformat} > cqlsh:test> create table static_table(id int, stat int static, ord int, val > text, primary key(id,ord)); > cqlsh:test> insert into static_table (id,stat,ord,val) VALUES ( 1, 1, 1, '1'); > cqlsh:test> delete from static_table where id=1 and ord=1 if stat != 1; > Invalid syntax at line 1, char 55 > delete from static_table where id=1 and ord=1 if stat != 1; > ^ > {noformat} > Same error if using =, <, <=, >= or > condition > According to [~thobbs] the syntax should work. Plus, the error message is > wrong -- This message was sent by Atlassian JIRA (v6.3.4#6332)