cassandra-commits mailing list archives

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

    [ https://issues.apache.org/jira/browse/CASSANDRA-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067931#comment-13067931
] 

Sylvain Lebresne commented on CASSANDRA-2912:
---------------------------------------------

A usingClauseDeleteObject is either TIMESTAMP or CONSISTENCY, so you at least want to allow
setting both of them. Now if the question was why * instead of ? at the end, then it's mostly
because I copied/pasted/modified usingClause where the * didn't seem to be a problem. I kind
of think that having a * even if more than 2 doesn't make much sense is no big deal and will
avoid, when we add a third possible usingClauseDeleteObjective, to be limited to 2 clauses
just because we forgot that it was limited to 2 previously. But I don't really feel strongly
about that.

> CQL ignores client timestamp for full row deletion
> --------------------------------------------------
>
>                 Key: CASSANDRA-2912
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2912
>             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: http://www.atlassian.com/software/jira

        

Mime
View raw message