You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Julien (JIRA)" <ji...@apache.org> on 2018/06/14 10:21:00 UTC
[jira] [Created] (CASSANDRA-14521) With server-generated
timestamps, INSERT after DELETE may not be applied
Julien created CASSANDRA-14521:
----------------------------------
Summary: With server-generated timestamps, INSERT after DELETE may not be applied
Key: CASSANDRA-14521
URL: https://issues.apache.org/jira/browse/CASSANDRA-14521
Project: Cassandra
Issue Type: Bug
Reporter: Julien
We use server-generated timestamps for all requests because of CASSANDRA-14304.
The scenario is basically the following:
{code}
INSERT INTO mytable(id) VALUES ('1');
DELETE FROM mytable WHERE id='1';
INSERT INTO mytable(id) VALUES ('1');
SELECT * FROM mytable WHERE id='1';
{code}
SELECT _sometimes_ does not return anything when the java driver has {{CassandraClientConnector.with(ServerSideTimestampGenerator.INSTANCE);}} and the Cassandra cluster has 3 nodes and replication-factor:3.
This scenario actually works as expected with CQL because I don't know how to force the usage of server-generated timestamps with CQL. Is it possible?
It also works correctly with a single Cassandra node.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org