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

            relates to

            Improvement - An improvement or enhancement to an existing feature or task. OP-103 DB Size and opush size

            • Normal - Between Minor and Major (is not a regression but is not trivial, this is a normal bug)
            • Closed - The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              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 ..................
              Hide
              Permalink
              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
              Hide
              Permalink
              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