Uploaded image for project: 'Kudu'
  1. Kudu
  2. KUDU-1431

Optimize History GC for Compliance Oriented Use Cases

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None
    • None

    Description

      Many compliance based use cases require prompt removal of select data from disk, including all history. In practice this can require both row deletes and erasing or masking of data within a column.

      The initial version of tablet history GC being worked on in KUDU-236 will not be able to support the SLA of such compliance oriented use cases. This request is to address improving the ability of tablet history GC to accommodate these types of deletes within a very short period of time (1-3 days). Ideally this could be configured on a transaction level, since not all record updates on a table are for compliance reasons.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              jtbirdsell Jordan Birdsell
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: