Investigate fast truncate solution with new aggregate time information only in in-memory structures.

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • 8

      Present Aggregate time-window doesn't seem to be enough to support fast truncate. Investigate maintaining the extra time window information required only as part of in-memory structures so that there will not be an issue with upgrade or downgrade.

      We need newest_start_ts and newest_start_txn in aggregated time windows to support fast truncate option.

              Assignee:
              [DO NOT USE] Backlog - Storage Engines Team
              Reporter:
              Vamsi Boyapati
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: