[
https://issues.apache.org/jira/browse/PHOENIX-7587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani resolved PHOENIX-7587.
-----------------------------------
Resolution: Fixed
> Revert configuring Table level MaxLookBack in syscat
> ----------------------------------------------------
>
> Key: PHOENIX-7587
> URL: https://issues.apache.org/jira/browse/PHOENIX-7587
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 5.3.0
> Reporter: Tanuj Khurana
> Assignee: Sanjeet Malhotra
> Priority: Blocker
> Fix For: 5.3.0
>
>
> PHOENIX-7314 introduced the compaction on flushes. This was important to
> avoid writing multiple versions of the same row to the storefile. However,
> PHOENIX-7402 removed the preFlush hook because we couldn't query syscat to
> get the PTable object in the context of flush. We needed the PTable in
> preFlush only to determine the table level maxlookback. However, the table
> level maxlookback feature introduced in PHOENIX-7006 can be achieved by just
> using ALTER DDL. For example,
> {code:java}
> ALTER TABLE TEST.T1 SET "phoenix.max.lookback.age.seconds"=0;{code}
> This saves the maxlookback in HBase table descriptor and we can access it
> easily during compaction and flushes.
> For applications which do frequent row updates while the row is still in
> memstore it is important to have compaction on flushes. So this Jira proposes
> to revert the table-level maxlookback feature.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
