[jira] [Updated] (PHOENIX-5518) Unittests for global index read repair count
[ https://issues.apache.org/jira/browse/PHOENIX-5518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geoffrey Jacoby updated PHOENIX-5518: - Fix Version/s: 5.2.1 (was: 4.17.0) (was: 5.2.0) (was: 4.16.2) > 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: 5.2.1 > > > [~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)
[jira] [Updated] (PHOENIX-5518) Unittests for global index read repair count
[ https://issues.apache.org/jira/browse/PHOENIX-5518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal updated PHOENIX-5518: --- Fix Version/s: (was: 5.1.2) > 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.3.4#803005)
[jira] [Updated] (PHOENIX-5518) Unittests for global index read repair count
[ https://issues.apache.org/jira/browse/PHOENIX-5518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viraj Jasani updated PHOENIX-5518: -- Fix Version/s: (was: 4.16.1) 4.16.2 5.1.2 5.2.0 > 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, 5.1.2, 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.3.4#803005)
[jira] [Updated] (PHOENIX-5518) Unittests for global index read repair count
[ https://issues.apache.org/jira/browse/PHOENIX-5518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-5518: --- Fix Version/s: (was: 4.15.1) > 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: 5.1.0, 4.16.1, 4.17.0 > > > [~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.3.4#803005)
[jira] [Updated] (PHOENIX-5518) Unittests for global index read repair count
[ https://issues.apache.org/jira/browse/PHOENIX-5518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-5518: --- Fix Version/s: 4.17.0 > 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: 5.1.0, 4.15.1, 4.16.1, 4.17.0 > > > [~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.3.4#803005)
[jira] [Updated] (PHOENIX-5518) Unittests for global index read repair count
[ https://issues.apache.org/jira/browse/PHOENIX-5518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-5518: --- Fix Version/s: (was: 4.16.0) 4.16.1 > 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: 5.1.0, 4.15.1, 4.16.1 > > > [~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.3.4#803005)
[jira] [Updated] (PHOENIX-5518) Unittests for global index read repair count
[ https://issues.apache.org/jira/browse/PHOENIX-5518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xinyi Yan updated PHOENIX-5518: --- Fix Version/s: 4.16.0 > 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: 5.1.0, 4.15.1, 4.16.0 > > > [~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.3.4#803005)
[jira] [Updated] (PHOENIX-5518) Unittests for global index read repair count
[ https://issues.apache.org/jira/browse/PHOENIX-5518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-5518: --- Fix Version/s: 4.15.1 5.1.0 > 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: 5.1.0, 4.15.1 > > > [~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.3.4#803005)
[jira] [Updated] (PHOENIX-5518) Unittests for global index read repair count
[ https://issues.apache.org/jira/browse/PHOENIX-5518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-5518: -- Affects Version/s: (was: 4.15.0) > 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 > > [~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.3.4#803005)
[jira] [Updated] (PHOENIX-5518) Unittests for global index read repair count
[ https://issues.apache.org/jira/browse/PHOENIX-5518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-5518: -- Fix Version/s: (was: 4.15.0) > Unittests for global index read repair count > > > Key: PHOENIX-5518 > URL: https://issues.apache.org/jira/browse/PHOENIX-5518 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Kadir OZDEMIR >Priority: Major > > [~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.3.4#803005)
[jira] [Updated] (PHOENIX-5518) Unittests for global index read repair count
[ https://issues.apache.org/jira/browse/PHOENIX-5518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-5518: -- Fix Version/s: 4.15.0 > 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.15.0 > > > [~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.3.4#803005)
[jira] [Updated] (PHOENIX-5518) Unittests for global index read repair count
[ https://issues.apache.org/jira/browse/PHOENIX-5518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chinmay Kulkarni updated PHOENIX-5518: -- Affects Version/s: 4.15.0 > Unittests for global index read repair count > > > Key: PHOENIX-5518 > URL: https://issues.apache.org/jira/browse/PHOENIX-5518 > Project: Phoenix > Issue Type: Improvement >Affects Versions: 4.15.0 >Reporter: Lars Hofhansl >Assignee: Kadir OZDEMIR >Priority: Major > Fix For: 4.15.0 > > > [~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.3.4#803005)
