[
https://issues.apache.org/jira/browse/CASSANDRA-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067936#comment-13067936
]
Pavel Yaskevich commented on CASSANDRA-2912:
--------------------------------------------
I'm asking because that also means that user will be able to specify as many
timestamps and consistency levels as he wants, we will need to split
usingClauseDeleteObjective into two statements - one for consistency level and
one for timestamp and use them in usingClauseDelete like (K_USING
usingConsistencyLevel[attrs] (K_AND usingTimestamp[attrs])? ) to support
language consistency.
> 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
