Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-14521

With server-generated timestamps, INSERT after DELETE may not be applied

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      We use server-generated timestamps for all requests because of CASSANDRA-14304.

      The scenario is basically the following:

      INSERT INTO mytable(id) VALUES ('1');
      DELETE FROM mytable  WHERE id='1';
      INSERT INTO mytable(id) VALUES ('1');
      SELECT * FROM mytable WHERE id='1';
      

      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.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              Julien Moreau Genesys Julien
            • Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated: