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

add table options required_ttl and max_ttl

Agile BoardAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsAdd voteVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • All
    • None

    Description

      This is related to CASSANDRA-9420

      For use cases where applications know an upper bound on TTL or know that all TTLs are the same value, if this is put into the schema then we can choose to skip cells past these TTL values rather than converting them to tombstones.

      For this to work, we would need these fixed and immutable once set into the table, but would need to allow tables to add this after the fact (alter table).

      For all new data, the TTLs would need to be checked to make sure that they respect the expected property (the ttl is required_ttl if defined, or <= max_ttl if defined). For existing data, we could ether validate the TTL matches the expected setting and drop the cell, or we could detect that it doesn’t match, and fall back to tombstone (see org.apache.cassandra.db.rows.AbstractCell#purge).

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned Assign to me
            dcapwell David Capwell

            Dates

              Created:
              Updated:

              Slack

                Issue deployment