You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Eric Evans (JIRA)" <ji...@apache.org> on 2011/01/20 23:12:44 UTC

[jira] Resolved: (CASSANDRA-1706) CQL deletes (aka DELETE)

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

Eric Evans resolved CASSANDRA-1706.
-----------------------------------

    Resolution: Fixed
      Assignee: Eric Evans

I believe this to be complete at this point.

> CQL deletes (aka DELETE)
> ------------------------
>
>                 Key: CASSANDRA-1706
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1706
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: API
>    Affects Versions: 0.8
>            Reporter: Eric Evans
>            Assignee: Eric Evans
>            Priority: Minor
>             Fix For: 0.8
>
>         Attachments: v2-0001-CASSANDRA-1706-CQL-DELETE-w-functional-tests.txt
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> CQL specification and implementation for data removal.
> This corresponds to the following RPC methods:
> * remove()
> * batch_mutate() (deleting, not updating)
> * truncate() (?)
> My thoughts on the syntax are that it can probably closely mirror a subset of `SELECT':
> {code:SQL}
> DELETE (FROM)? <CF> [USING CONSISTENCY.<LVL>] WHERE <EXPRESSION>
> {code}
> Optionally, you could support a form that makes the `WHERE' clause optional, statements without the clause would be interpreted as a column family truncation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.