[jira] [Updated] (CASSANDRA-7067) Refuse CAS batch that have a 'USING TIMESTAMP'
[
https://issues.apache.org/jira/browse/CASSANDRA-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Hanna updated CASSANDRA-7067:
Labels: LWT lhf (was: lhf)
> Refuse CAS batch that have a 'USING TIMESTAMP'
> --
>
> Key: CASSANDRA-7067
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7067
> Project: Cassandra
> Issue Type: Sub-task
>Reporter: Mikhail Stepura
>Assignee: Sylvain Lebresne
>Priority: Minor
> Labels: LWT, lhf
> Fix For: 2.0.9
>
> Attachments: 7067.txt
>
>
> Cassandra must refuse BATCHes with {{TIMESTAMP}}, if they contain a CAS
> statement(s). Like this one:
> {code}
> BEGIN BATCH USING TIMESTAMP
> INSERT INTO users (id, firstname, lastname) VALUES (999, 'Jack', 'Sparrow')
> IF NOT EXISTS
> APPLY BATCH
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-7067) Refuse CAS batch that have a 'USING TIMESTAMP'
[
https://issues.apache.org/jira/browse/CASSANDRA-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-7067:
Attachment: 7067.txt
Attaching a patch for 2.0 that, in the spirit of CASSANDRA-6649, don't yet
refuse the query but warn in the log that 1) the use of timestamp is incorrect
and has been ignored and 2) that such query will be refused completely in 2.1+.
I'll turns those to InvalidRequestException in 2.1 while merging upon commit.
The patch also refuse timestamps on counter batch while at it since that's also
invalid but was not handled by CASSANDRA-6649.
Refuse CAS batch that have a 'USING TIMESTAMP'
--
Key: CASSANDRA-7067
URL: https://issues.apache.org/jira/browse/CASSANDRA-7067
Project: Cassandra
Issue Type: Sub-task
Reporter: Mikhail Stepura
Priority: Minor
Labels: lhf
Fix For: 2.0.8
Attachments: 7067.txt
Cassandra must refuse BATCHes with {{TIMESTAMP}}, if they contain a CAS
statement(s). Like this one:
{code}
BEGIN BATCH USING TIMESTAMP
INSERT INTO users (id, firstname, lastname) VALUES (999, 'Jack', 'Sparrow')
IF NOT EXISTS
APPLY BATCH
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CASSANDRA-7067) Refuse CAS batch that have a 'USING TIMESTAMP'
[
https://issues.apache.org/jira/browse/CASSANDRA-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Stepura updated CASSANDRA-7067:
---
Labels: lhf (was: )
Refuse CAS batch that have a 'USING TIMESTAMP'
--
Key: CASSANDRA-7067
URL: https://issues.apache.org/jira/browse/CASSANDRA-7067
Project: Cassandra
Issue Type: Sub-task
Reporter: Mikhail Stepura
Priority: Minor
Labels: lhf
Fix For: 2.0.8, 2.1 beta2
Cassandra must refuse BATCHes with {{TIMESTAMP}}, if they contain a CAS
statement(s). Like this one:
{code}
BEGIN BATCH USING TIMESTAMP
INSERT INTO users (id, firstname, lastname) VALUES (999, 'Jack', 'Sparrow')
IF NOT EXISTS
APPLY BATCH
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CASSANDRA-7067) Refuse CAS batch that have a 'USING TIMESTAMP'
[
https://issues.apache.org/jira/browse/CASSANDRA-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Stepura updated CASSANDRA-7067:
---
Description:
Cassandra must refuse BATCHes with {{TIMESTAMP}}, if they contain a CAS
statement(s). Like this one:
{code}
BEGIN BATCH USING TIMESTAMP
INSERT INTO users (id, firstname, lastname) VALUES (999, 'Jack', 'Sparrow') IF
NOT EXISTS
APPLY BATCH
{code}
was:
Cassandra must refuse BATCHes with {{TIMESTMAP}}, if they contain a CAS
statement(s). Like this one:
{code}
BEGIN BATCH USING TIMESTAMP
INSERT INTO users (id, firstname, lastname) VALUES (999, 'Jack', 'Sparrow') IF
NOT EXISTS
APPLY BATCH
{code}
Refuse CAS batch that have a 'USING TIMESTAMP'
--
Key: CASSANDRA-7067
URL: https://issues.apache.org/jira/browse/CASSANDRA-7067
Project: Cassandra
Issue Type: Sub-task
Reporter: Mikhail Stepura
Priority: Minor
Fix For: 2.0.8, 2.1 beta2
Cassandra must refuse BATCHes with {{TIMESTAMP}}, if they contain a CAS
statement(s). Like this one:
{code}
BEGIN BATCH USING TIMESTAMP
INSERT INTO users (id, firstname, lastname) VALUES (999, 'Jack', 'Sparrow')
IF NOT EXISTS
APPLY BATCH
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
