You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Swaroopa Kadam (Jira)" <ji...@apache.org> on 2020/02/22 00:54:00 UTC
[jira] [Updated] (PHOENIX-5734) IndexScrutinyTool should not report
rows beyond maxLookBack age
[ https://issues.apache.org/jira/browse/PHOENIX-5734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Swaroopa Kadam updated PHOENIX-5734:
------------------------------------
Description:
Index Scrutiny tool should not report row mismatch if the row gets rewritten during the run and the last version around is beyond max look back age which will then get removed by compaction.
Or add another type of counters to separate invalid rows into BEYOND_MAX_LOOKBACK or similar
was:Index Scrutiny tool should not report row mismatch if the row gets rewritten during the run and the last version around is beyond max look back age which will then get removed by compaction.
> IndexScrutinyTool should not report rows beyond maxLookBack age
> ---------------------------------------------------------------
>
> Key: PHOENIX-5734
> URL: https://issues.apache.org/jira/browse/PHOENIX-5734
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Swaroopa Kadam
> Assignee: Swaroopa Kadam
> Priority: Major
>
> Index Scrutiny tool should not report row mismatch if the row gets rewritten during the run and the last version around is beyond max look back age which will then get removed by compaction.
>
> Or add another type of counters to separate invalid rows into BEYOND_MAX_LOOKBACK or similar
--
This message was sent by Atlassian Jira
(v8.3.4#803005)