Opush
  1. Opush
  2. OP-84

Ensure that data inserted into cassandra expire

    Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Normal Normal
    • Resolution: Fixed
    • Affects Version/s: 3.0.1
    • Fix Version/s: 3.0.2
    • Labels:
    • Rank:
      6410
    • Sprint:
      Sprint

      Description

      Current behavior:
      When opush insert data into the cassandra cluster, this data will never expire.

      Expected behavior:
      When opush insert data into the cassandra cluster, this data will expire automatically in 30 days.

        Issue Links

          Activity

          Thomas HILAIRE made changes -
          Field Original Value New Value
          Assignee Matthieu BAECHLER [ mbaechler@linagora.com ] Thomas HILAIRE [ thilaire@linagora.com ]
          Thomas HILAIRE made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          Thomas HILAIRE made changes -
          Labels 201409 GN
          Sprint Sprint [ 23 ]
          Thomas HILAIRE made changes -
          Status In Progress [ 3 ] In Review [ 10001 ]
          Thomas HILAIRE made changes -
          Status In Review [ 10001 ] Ready To Merge [ 10002 ]
          Resolution Fixed [ 1 ]
          Hide
          Thomas HILAIRE added a comment -

          Impact:

          • CRASH: connection
          • CRASH: first schema installation
          • CRASH: schema updates
          • OPUSH: none if the server migrates and restart as expected

          QA:
          Data should expire themself about 30 days, as you won't wait 30 days you can verify with a Cassandra request that data have a TTL after the migration.

          1

          For exemple, run this query using cqlsh :

          select ttl(analysed_sync_collection) from opush.synced_collection_v2 ;
          


          - before the migration the "ttle" value of columns should be null or 0 for every tables.


          - after the migration the "ttle" value of columns should be something like 30 days (in seconds) for every tables.

          2

          Every table must have a default TTL at 30 days:

          DESCRIBE TABLE opush.snapshot;
          CREATE TABLE snapshot (
            id uuid,
            snapshot text,
            PRIMARY KEY ((id))
          ) WITH
            bloom_filter_fp_chance=0.010000 AND
          ..................
            default_time_to_live=XXX AND
          ..................
          
          Show
          Thomas HILAIRE added a comment - Impact : CRASH: connection CRASH: first schema installation CRASH: schema updates OPUSH: none if the server migrates and restart as expected QA : Data should expire themself about 30 days, as you won't wait 30 days you can verify with a Cassandra request that data have a TTL after the migration. 1 For exemple, run this query using cqlsh : select ttl(analysed_sync_collection) from opush.synced_collection_v2 ; - before the migration the "ttle" value of columns should be null or 0 for every tables. - after the migration the "ttle" value of columns should be something like 30 days (in seconds) for every tables. 2 Every table must have a default TTL at 30 days: DESCRIBE TABLE opush.snapshot; CREATE TABLE snapshot ( id uuid, snapshot text, PRIMARY KEY ((id)) ) WITH bloom_filter_fp_chance=0.010000 AND .................. default_time_to_live=XXX AND ..................
          David Dolcimascolo made changes -
          Status Ready To Merge [ 10002 ] Resolved [ 5 ]
          Matthieu EXT_BAECHLER made changes -
          Link This issue relates to OP-103 [ OP-103 ]
          Hide
          Stephane COLSON added a comment -

          OK with version 3.0.2~beta3~git20141009.091827.60ca887-1

          Show
          Stephane COLSON added a comment - OK with version 3.0.2~beta3~git20141009.091827.60ca887-1
          Stephane COLSON made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          Hide
          Jenkins Continuous Integration Server added a comment -

          SUCCESS: Integrated in opush-master #156
          OP-84 Migration always retry read and write (thilaire: 692cc753bb841b46deb91120534f2ccfe0057b7a)

          • push-dao-cassandra/src/main/java/org/obm/push/cassandra/migration/coded/V2ToV3_TTL.java
          Show
          Jenkins Continuous Integration Server added a comment - SUCCESS: Integrated in opush-master #156 OP-84 Migration always retry read and write (thilaire: 692cc753bb841b46deb91120534f2ccfe0057b7a ) push-dao-cassandra/src/main/java/org/obm/push/cassandra/migration/coded/V2ToV3_TTL.java

            People

            • Assignee:
              Thomas HILAIRE
              Reporter:
              Thomas HILAIRE
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Agile