[
https://issues.apache.org/jira/browse/PHOENIX-5875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17134420#comment-17134420
]
Geoffrey Jacoby commented on PHOENIX-5875:
------------------------------------------
The test run seems to have crashed but had gotten most of the way done before
it did (it was in the splittable syscat tests), including having already run
the index tests. The release audit flag is for a test not related to this
patch.
> Optional logging for IndexTool verification
> -------------------------------------------
>
> Key: PHOENIX-5875
> URL: https://issues.apache.org/jira/browse/PHOENIX-5875
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 5.0.0, 4.14.3
> Reporter: Kadir OZDEMIR
> Assignee: Geoffrey Jacoby
> Priority: Major
> Fix For: 5.1.0, 4.16.0
>
> Attachments: PHOENIX-5875-4.x.v1.patch, PHOENIX-5875-4.x.v2.patch,
> PHOENIX-5875-4.x.v3.patch, PHOENIX-5875.v1.patch
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> IndexTool logs information about each row that has a verification failure.
> The amount of logging can be excessive for large index tables. Also for some
> runs, we may want to just do incremental repair, i.e., repair only the rows
> that are broken, using -v BOTH or -v BEFORE, but not interested in the
> details of how they are broken. Thus, IndexTool should have an option to
> disable logging, something like, -dl (--disable-logging) BEFORE | AFTER |
> BOTH where BEFORE, AFTER and BOTH indicate at the which phase (before or
> after index repair or a both phases ) logging is disabled.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
