cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1706) CQL deletes (aka DELETE)
Date Sat, 06 Nov 2010 20:42:23 GMT

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

Jonathan Ellis commented on CASSANDRA-1706:
-------------------------------------------

bq. Is there any reason this couldn't use identical syntax to `SELECT'?

There are two differences:

1. We don't support column slices on delete
2. We don't support deleting row ranges or indexed predicates

We could hide these by doing read-then-delete in the SQL layer but I'm not sure this is a
good idea, I would prefer to leave it out for version 1.

> 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
>            Priority: Minor
>             Fix For: 0.8
>
>   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.


Mime
View raw message