cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6237) Allow range deletions in CQL
Date Wed, 03 Sep 2014 19:55:52 GMT


Tyler Hobbs commented on CASSANDRA-6237:

bq. 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.

This ticket was created before CASSANDRA-6875, so multi-column relations didn't exist yet.

1) Refactor SelectStatement to make some part of it easily reusable
2) Refactor ModificationStatement to allow it to reuse the Restrictions logic form SelectStatement

I agree that we need (1), and some amount of (2) may be needed.

bq. The question being: do we extends the scope of this ticket or do we create one or two
others for those tasks?

I would personally try to keep all of the work in this ticket.  It's targeted for 3.0, so
we have plenty of time.  However, feel free to split the work into multiple commits for clarity.

bq. 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.

I'm not aware of anything big that's pending, is there something specific you had in mind?

> Allow range deletions in CQL
> ----------------------------
>                 Key: CASSANDRA-6237
>                 URL:
>             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

View raw message