[
https://issues.apache.org/jira/browse/CASSANDRA-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14630464#comment-14630464
]
Jim Witschey commented on CASSANDRA-6237:
-----------------------------------------
It's not clear to me why some user function tests changed, e.g.
[here|https://github.com/apache/cassandra/compare/trunk...blerer:6237-trunk#diff-8115d8e7978dd79bc5dc30fe7459cca0R318]
and
[here|https://github.com/apache/cassandra/compare/trunk...blerer:6237-trunk#diff-0c3390617044fd3bd9a25bc5ed950dffR100].
Are these in scope for this ticket?
Other than that, though, +1 from me. My dtests pass, and the unit tests look
quite thorough. I don't think merging these dtests into the test suite will be
necessary, unless you do.
> 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)