phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoffrey Jacoby (Jira)" <j...@apache.org>
Subject [jira] [Created] (PHOENIX-6071) Table-specific Max Lookback Age
Date Tue, 11 Aug 2020 21:21:00 GMT
Geoffrey Jacoby created PHOENIX-6071:
----------------------------------------

             Summary: Table-specific Max Lookback Age
                 Key: PHOENIX-6071
                 URL: https://issues.apache.org/jira/browse/PHOENIX-6071
             Project: Phoenix
          Issue Type: Improvement
            Reporter: Geoffrey Jacoby
             Fix For: 5.1.1, 4.16.0


PHOENIX-5645 / PHOENIX-5881 introduced max lookback age, which prevents all mutations from
being purged by major compaction for a fixed moving window of time. These earlier JIRAs had
a single cluster-wide window, but operators may want to vary this for different tables (or
exempt some entirely). 

This is especially important given max lookback age's interactions with HBase TTL where due
to nature of the HBase compaction hooks, an HBase TTL will override the max lookback age to
be max(TTL, max lookback age), which might be longer than operators want for a particular
table. For tables with no indexes that have HBase TTLs, operators will likely want to turn
max lookback age off for them. 





--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message