[CASSANDRA-6237] Allow range deletions in CQL

• Type: Improvement
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 3.0 beta 2
• Component/s: Legacy/CQL
• Labels: cql docs
• Assignee: Benjamin Lerer Assign to me
• Reporter: Sylvain Lebresne

Authors

Benjamin Lerer

Reviewers

Joshua McKenzie

• Tester: Jim Witschey
• Created: 24/Oct/13 13:16
• Updated: 16/Apr/19 09:32
• Resolved: 04/Sep/15 19:19

Description

We uses RangeTombstones internally in a number of places, but we could expose more directly too. Typically, given a table like:

CREATE TABLE events (
    id text,
    created_at timestamp,
    content text,
    PRIMARY KEY (id, created_at)
)

we could allow queries like:

DELETE FROM events WHERE id='someEvent' AND created_at < 'Jan 3, 2013';

Issue Links

• depends upon: CASSANDRA-9759 RowAndTombstoneMergeIterator combine RangeTombstones even if they should not be
• depends upon: CASSANDRA-7651 Tolerate min/max column names of different lengths for slice intersections
• is blocked by: CASSANDRA-8099 Refactor and modernize the storage engine
• is duplicated by: CASSANDRA-8284 delete columns using range
• is duplicated by: CASSANDRA-6173 Unable to delete multiple entries using In clause on clustering part of compound key
• is duplicated by: CASSANDRA-6292 CQL should be able to do a delete with a > or < operator on a clustering portion of a primary key
• is duplicated by: CASSANDRA-7097 Allow deleting over composite
• is duplicated by: CASSANDRA-8397 Support UPDATE with IN requirement for clustering key
• relates to: CASSANDRA-8603 Cut tombstone memory footprint in half for cql deletes
• requires: CASSANDRA-7981 Refactor SelectStatement