[
https://issues.apache.org/jira/browse/PHOENIX-5518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17554681#comment-17554681
]
Geoffrey Jacoby commented on PHOENIX-5518:
------------------------------------------
I checked and it appears that this is still the case. We have tests for the
repair counts when running the IndexTool, and we have unit tests that verify
that the GlobalIndexChecker's metrics are hooked up correctly. However, we
don't appear to have an IT test that forces GlobalIndexChecker to do some
in-line read repairs and verifies the counter is as expected.
Doesn't seem like a blocker for 5.2 though, so I'll push out to the next
release unless someone has bandwidth to take this in the short term
> Unittests for global index read repair count
> --------------------------------------------
>
> Key: PHOENIX-5518
> URL: https://issues.apache.org/jira/browse/PHOENIX-5518
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Lars Hofhansl
> Assignee: Kadir OZDEMIR
> Priority: Major
> Fix For: 4.17.0, 5.2.0, 4.16.2
>
>
> [~kadir] and I were tracking down a scenario where the read repair kept
> increasing.
> It turned out not to be a bug, but we realized that there is not test that
> checks whether the read repair count is as expected as correctness is
> guaranteed in any case.
> So let's add a test case based on the read repairs metric we added some time
> back.
> I will not have time to work in, just filing in case somebody has.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
