[
https://issues.apache.org/jira/browse/CASSANDRA-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119521#comment-14119521
]
Benjamin Lerer commented on CASSANDRA-6237:
-------------------------------------------
The scope of the ticket, as I understand it, is to support slicing on the last
clustering column specified within the query. It seems to me that adding
support for multi-column relations goes beyond that.
Ideally what we would want is to be able to support all the possible
combinations supported by SelectStatement for delete and update but this
require in my opinion to:
1) Refactor SelectStatement to make some part of it easily reusable
2) Refactor ModificationStatement to allow it to reuse the Restrictions logic
form SelectStatement
The question being: do we extends the scope of this ticket or do we create one
or two others for those tasks?
I also think it will be good if we make sure first that all the pending patch
affecting SelectStatement are commited before we try to refactor it.
> 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
>
> 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)
