Viraj Jasani created PHOENIX-7657:
-------------------------------------
Summary: Eventually consistent TTL expiry - Disable
TTLRegionScanner
Key: PHOENIX-7657
URL: https://issues.apache.org/jira/browse/PHOENIX-7657
Project: Phoenix
Issue Type: Improvement
Reporter: Viraj Jasani
Phoenix provides strongly consistent TTL expiration i.e. soon after the TTL of
the given row is expired, the row is no longer visible to the client performing
scan operation on the table. This is achieved by masking mechanism implemented
in TTLRegionScanner by default.
Some clients might prefer keeping the row visible for scans, until it is
expired by the major compaction after the TTL expiry. This gives the effect of
eventually consistent TTL expiration.
One way to disable the scan masking behavior is by setting
"phoenix.compaction.enabled" to "false". However, this is not advisable as it
will also disable CompactionScanner, which is risky.
The purpose of this Jira is to introduce new hbase-site config
"phoenix.ttl.scan.masking.enabled" with default value as "true". This config
value can be set to "false" for specific tables, thereby allowing the table
scans to see the rows even after their TTL expiry, until the row is eventually
expired from the disk by major compaction.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
