[jira] [Comment Edited] (CASSANDRA-6237) Allow range deletions in CQL

["Benjamin Lerer (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631193#comment-14631193 ] 

Benjamin Lerer edited comment on CASSANDRA-6237 at 7/17/15 11:07 AM:
---------------------------------------------------------------------

{quote}It's not clear to me why some user function tests changed, e.g. here and here. Are these in scope for this ticket?{quote}

Statements are processed in 2 phases. They are prepared and then executed. We try to preform the validation, as much as possible, in the preparation phase. It was not always the case for Insert/Update/Delete statements. I fixed that in my patch.

Some of the unit tests were using invalid statements but as they were only testing the preparation phase no errors were thrown.
After my patch it was no longer the case. So, I had to make sure that the statements were valid.
 


was (Author: blerer):
{quote}It's not clear to me why some user function tests changed, e.g. here and here. Are these in scope for this ticket?{quote}

Statements are processed in 2 phases. They are prepared and then executed. We try to preform the validation as much as possible in the preparation phase. It was not always the case for Insert/Update/Delete statements. I fixed that in my patch.

Some of the unit tests were using invalid statements but as they were only testing the preparation phase no errors were thrown.
After my patch it was no longer the case. So I had to make sure that the statements were valid.
 

> Allow range deletions in CQL
> ----------------------------
>
>                 Key: CASSANDRA-6237
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6237
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Sylvain Lebresne
>            Assignee: Benjamin Lerer
>            Priority: Minor
>              Labels: cql, docs
>             Fix For: 3.0.0 rc1
>
>         Attachments: CASSANDRA-6237.txt
>
>
> We uses RangeTombstones internally in a number of places, but we could expose more directly too. Typically, given a table like:
> {noformat}
> CREATE TABLE events (
>     id text,
>     created_at timestamp,
>     content text,
>     PRIMARY KEY (id, created_at)
> )
> {noformat}
> we could allow queries like:
> {noformat}
> DELETE FROM events WHERE id='someEvent' AND created_at < 'Jan 3, 2013';
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)