cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2912) CQL ignores client timestamp for full row deletion
Date Tue, 19 Jul 2011 21:10:57 GMT


Sylvain Lebresne commented on CASSANDRA-2912:

bq. I'm asking because that also means that user will be able to specify as many timestamps
and consistency levels as he wants

That's what I said. To rephrase:
* it's the case also for the UPDATE statement: we should do something for both or none.
* I personally don't think it's a problem, the last statement would be picked each time, which
feels a reasonable behavior in that case. More precisely I don't think it's worth caring about.
* if we do want to add a restriction though, I think it would be easier to have Attributes
throw an exception when one of its set method is called twice. Because your proposed fix will
become a bit ugly for the UPDATE statement and it would be a pain to extend to future new

> CQL ignores client timestamp for full row deletion
> --------------------------------------------------
>                 Key: CASSANDRA-2912
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8.1
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>              Labels: cql
>             Fix For: 0.8.2
>         Attachments: 0001-CQL-timestamp-row-deletion.patch

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message