[jira] [Resolved] (PHOENIX-6288) Minicluster startup problems on Jenkins

2020-12-30 Thread Istvan Toth (Jira)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Istvan Toth resolved PHOENIX-6288.
--
Fix Version/s: 4.16.0
   5.1.0
   Resolution: Fixed

Committed to master and 4.x
Thanks for the reviews [~gjacoby] and shahrs87.

Fingers crossed that this is enough to improve the situation.

> Minicluster startup problems on Jenkins
> ---
>
> Key: PHOENIX-6288
> URL: https://issues.apache.org/jira/browse/PHOENIX-6288
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Critical
> Fix For: 5.1.0, 4.16.0
>
>
> We are sporadically getting Test failures on Jenkins that are caused by the 
> miniCluster startup timeouts.
> {noformat}
> Caused by: java.lang.RuntimeException: Master not active after 3ms at 
> org.apache.hadoop.hbase.util.JVMClusterUtil.waitForEvent(JVMClusterUtil.java:232)
>  
> at 
> org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:188)
> at 
> org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:430) 
> at org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:259) 
> ... 43 more
> {noformat}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (PHOENIX-6290) Extend IndexRegionSplitPolicy from SteppingSplitPolicy on master

2020-12-30 Thread Istvan Toth (Jira)
Istvan Toth created PHOENIX-6290:


 Summary: Extend IndexRegionSplitPolicy from SteppingSplitPolicy on 
master
 Key: PHOENIX-6290
 URL: https://issues.apache.org/jira/browse/PHOENIX-6290
 Project: Phoenix
  Issue Type: Bug
  Components: core
Affects Versions: 5.0.0
Reporter: Istvan Toth
Assignee: Istvan Toth


IndexRegionSplitPolicy hasn't been updated to inherint SteppingSplitPolicy.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (PHOENIX-6289) Flaky test UpsertSelectIT.testUpsertSelectWithNoIndex

2020-12-30 Thread Viraj Jasani (Jira)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Viraj Jasani updated PHOENIX-6289:
--
Fix Version/s: 4.16.0
   5.1.0

> Flaky test UpsertSelectIT.testUpsertSelectWithNoIndex
> -
>
> Key: PHOENIX-6289
> URL: https://issues.apache.org/jira/browse/PHOENIX-6289
> Project: Phoenix
>  Issue Type: Test
>Affects Versions: 5.0.0, 4.15.0
>Reporter: Viraj Jasani
>Assignee: Viraj Jasani
>Priority: Major
> Fix For: 5.1.0, 4.16.0
>
>
> UpsertSelectIT.testUpsertSelectWithNoIndex is flapping at times due to no of 
> open connections is not always 0 by the end of the test.
> {code:java}
> java.lang.AssertionError: expected:<0> but was:<1>
>   at org.junit.Assert.fail(Assert.java:89)
>   at org.junit.Assert.failNotEquals(Assert.java:835)
>   at org.junit.Assert.assertEquals(Assert.java:647)
>   at org.junit.Assert.assertEquals(Assert.java:633)
>   at 
> org.apache.phoenix.end2end.UpsertSelectIT.assertNoConnLeak(UpsertSelectIT.java:90)
> {code}
> e.g 
> https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/4.x/163/testReport/org.apache.phoenix.end2end/UpsertSelectIT/MatrixBuild___Matrix___HBASE_PROFILE1_4BuildAndTest___testUpsertSelectWithNoIndex_UpsertSelecttIT_allowServerSideMutations_true_/



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (PHOENIX-6289) Flaky test UpsertSelectIT.testUpsertSelectWithNoIndex

2020-12-30 Thread Viraj Jasani (Jira)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Viraj Jasani reassigned PHOENIX-6289:
-

Assignee: Viraj Jasani

> Flaky test UpsertSelectIT.testUpsertSelectWithNoIndex
> -
>
> Key: PHOENIX-6289
> URL: https://issues.apache.org/jira/browse/PHOENIX-6289
> Project: Phoenix
>  Issue Type: Test
>Reporter: Viraj Jasani
>Assignee: Viraj Jasani
>Priority: Major
>
> UpsertSelectIT.testUpsertSelectWithNoIndex is flapping at times due to no of 
> open connections is not always 0 by the end of the test.
> {code:java}
> java.lang.AssertionError: expected:<0> but was:<1>
>   at org.junit.Assert.fail(Assert.java:89)
>   at org.junit.Assert.failNotEquals(Assert.java:835)
>   at org.junit.Assert.assertEquals(Assert.java:647)
>   at org.junit.Assert.assertEquals(Assert.java:633)
>   at 
> org.apache.phoenix.end2end.UpsertSelectIT.assertNoConnLeak(UpsertSelectIT.java:90)
> {code}
> e.g 
> https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/4.x/163/testReport/org.apache.phoenix.end2end/UpsertSelectIT/MatrixBuild___Matrix___HBASE_PROFILE1_4BuildAndTest___testUpsertSelectWithNoIndex_UpsertSelecttIT_allowServerSideMutations_true_/



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (PHOENIX-6289) Flaky test UpsertSelectIT.testUpsertSelectWithNoIndex

2020-12-30 Thread Viraj Jasani (Jira)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Viraj Jasani updated PHOENIX-6289:
--
Affects Version/s: 5.0.0
   4.15.0

> Flaky test UpsertSelectIT.testUpsertSelectWithNoIndex
> -
>
> Key: PHOENIX-6289
> URL: https://issues.apache.org/jira/browse/PHOENIX-6289
> Project: Phoenix
>  Issue Type: Test
>Affects Versions: 5.0.0, 4.15.0
>Reporter: Viraj Jasani
>Assignee: Viraj Jasani
>Priority: Major
>
> UpsertSelectIT.testUpsertSelectWithNoIndex is flapping at times due to no of 
> open connections is not always 0 by the end of the test.
> {code:java}
> java.lang.AssertionError: expected:<0> but was:<1>
>   at org.junit.Assert.fail(Assert.java:89)
>   at org.junit.Assert.failNotEquals(Assert.java:835)
>   at org.junit.Assert.assertEquals(Assert.java:647)
>   at org.junit.Assert.assertEquals(Assert.java:633)
>   at 
> org.apache.phoenix.end2end.UpsertSelectIT.assertNoConnLeak(UpsertSelectIT.java:90)
> {code}
> e.g 
> https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/4.x/163/testReport/org.apache.phoenix.end2end/UpsertSelectIT/MatrixBuild___Matrix___HBASE_PROFILE1_4BuildAndTest___testUpsertSelectWithNoIndex_UpsertSelecttIT_allowServerSideMutations_true_/



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (PHOENIX-6289) Flaky test UpsertSelectIT.testUpsertSelectWithNoIndex

2020-12-30 Thread Viraj Jasani (Jira)
Viraj Jasani created PHOENIX-6289:
-

 Summary: Flaky test UpsertSelectIT.testUpsertSelectWithNoIndex
 Key: PHOENIX-6289
 URL: https://issues.apache.org/jira/browse/PHOENIX-6289
 Project: Phoenix
  Issue Type: Test
Reporter: Viraj Jasani


UpsertSelectIT.testUpsertSelectWithNoIndex is flapping at times due to no of 
open connections is not always 0 by the end of the test.
{code:java}
java.lang.AssertionError: expected:<0> but was:<1>
at org.junit.Assert.fail(Assert.java:89)
at org.junit.Assert.failNotEquals(Assert.java:835)
at org.junit.Assert.assertEquals(Assert.java:647)
at org.junit.Assert.assertEquals(Assert.java:633)
at 
org.apache.phoenix.end2end.UpsertSelectIT.assertNoConnLeak(UpsertSelectIT.java:90)
{code}
e.g 
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/4.x/163/testReport/org.apache.phoenix.end2end/UpsertSelectIT/MatrixBuild___Matrix___HBASE_PROFILE1_4BuildAndTest___testUpsertSelectWithNoIndex_UpsertSelecttIT_allowServerSideMutations_true_/



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (PHOENIX-6286) Extend syscat RegionSplitPolicies from the default Policy for the HBase branch

2020-12-30 Thread Istvan Toth (Jira)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Istvan Toth resolved PHOENIX-6286.
--
Fix Version/s: 4.16.0
   5.1.0
   Resolution: Fixed

Committed to master and 4.x.
Thanks for the reviews [~vjasani] and [~gjacoby]

> Extend syscat RegionSplitPolicies from the default Policy for the HBase branch
> --
>
> Key: PHOENIX-6286
> URL: https://issues.apache.org/jira/browse/PHOENIX-6286
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
> Fix For: 5.1.0, 4.16.0
>
>
> The Syscat-specific Policies are exended from ConstantSizeRegionSplitPolicy, 
> instead of the default Policy for HBase.
> AFAICT this has historical, rather than technical reasons.
> Base our policies on the default policy for the supported HBase branch.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (PHOENIX-6288) Minicluster startup problems on Jenkins

2020-12-30 Thread Istvan Toth (Jira)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Istvan Toth updated PHOENIX-6288:
-
Description: 
We are sporadically getting Test failures on Jenkins that are caused by the 
miniCluster startup timeouts.
{noformat}
Caused by: java.lang.RuntimeException: Master not active after 3ms at 
org.apache.hadoop.hbase.util.JVMClusterUtil.waitForEvent(JVMClusterUtil.java:232)
 
at org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:188)
at 
org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:430) 
at org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:259) 
... 43 more
{noformat}
 

  was:
We are sporadically getting Test failures on Jenkins that are caused by the 
miniCluster startup timeouts.
{noformat}
Caused by: java.lang.RuntimeException: Master not active after 3ms at 
org.apache.hadoop.hbase.util.JVMClusterUtil.waitForEvent(JVMClusterUtil.java:232)
 at org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:188)
at 
org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:430) 
at org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:259) ... 
43 more{noformat}
 


> Minicluster startup problems on Jenkins
> ---
>
> Key: PHOENIX-6288
> URL: https://issues.apache.org/jira/browse/PHOENIX-6288
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Critical
>
> We are sporadically getting Test failures on Jenkins that are caused by the 
> miniCluster startup timeouts.
> {noformat}
> Caused by: java.lang.RuntimeException: Master not active after 3ms at 
> org.apache.hadoop.hbase.util.JVMClusterUtil.waitForEvent(JVMClusterUtil.java:232)
>  
> at 
> org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:188)
> at 
> org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:430) 
> at org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:259) 
> ... 43 more
> {noformat}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (PHOENIX-6288) Minicluster startup problems on Jenkins

2020-12-30 Thread Istvan Toth (Jira)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Istvan Toth updated PHOENIX-6288:
-
Description: 
We are sporadically getting Test failures on Jenkins that are caused by the 
miniCluster startup timeouts.
{noformat}
Caused by: java.lang.RuntimeException: Master not active after 3ms at 
org.apache.hadoop.hbase.util.JVMClusterUtil.waitForEvent(JVMClusterUtil.java:232)
 at org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:188)
at 
org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:430) 
at org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:259) ... 
43 more{noformat}
 

  was:
We are sporadically getting Test failures on Jenkins that are caused by the 
miniCluster startup timeouts.
{noformat}
Caused by: java.lang.RuntimeException: Master not active after 3ms at 
org.apache.hadoop.hbase.util.JVMClusterUtil.waitForEvent(JVMClusterUtil.java:232)
 at 
org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:188) at 
org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:430) 
at org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:259) ... 
43 more{noformat}
 


> Minicluster startup problems on Jenkins
> ---
>
> Key: PHOENIX-6288
> URL: https://issues.apache.org/jira/browse/PHOENIX-6288
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Critical
>
> We are sporadically getting Test failures on Jenkins that are caused by the 
> miniCluster startup timeouts.
> {noformat}
> Caused by: java.lang.RuntimeException: Master not active after 3ms at 
> org.apache.hadoop.hbase.util.JVMClusterUtil.waitForEvent(JVMClusterUtil.java:232)
>  at 
> org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:188)
> at 
> org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:430) 
> at org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:259) 
> ... 43 more{noformat}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (PHOENIX-6288) Minicluster startup problems on Jenkins

2020-12-30 Thread Istvan Toth (Jira)
Istvan Toth created PHOENIX-6288:


 Summary: Minicluster startup problems on Jenkins
 Key: PHOENIX-6288
 URL: https://issues.apache.org/jira/browse/PHOENIX-6288
 Project: Phoenix
  Issue Type: Bug
Reporter: Istvan Toth
Assignee: Istvan Toth


We are sporadically getting Test failures on Jenkins that are caused by the 
miniCluster startup timeouts.
{noformat}
Caused by: java.lang.RuntimeException: Master not active after 3ms at 
org.apache.hadoop.hbase.util.JVMClusterUtil.waitForEvent(JVMClusterUtil.java:232)
 at 
org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:188) at 
org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:430) 
at org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:259) ... 
43 more{noformat}
 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (PHOENIX-6287) Fix incorrect log in ParallelIterators.submitWork

2020-12-30 Thread chenglei (Jira)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

chenglei reassigned PHOENIX-6287:
-

Assignee: chenglei

> Fix incorrect log  in ParallelIterators.submitWork
> --
>
> Key: PHOENIX-6287
> URL: https://issues.apache.org/jira/browse/PHOENIX-6287
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 5.1.0, 4.16.0
>Reporter: chenglei
>Assignee: chenglei
>Priority: Major
> Fix For: 4.16.0, 5.10
>
> Attachments: PHOENIX-6287-4.x.patch
>
>
> In {{ParallelIterators.submitWork}}, the following log is critical but is 
> meaningless:
> {code:java}
> 123@Override
> 124public PeekingResultIterator call() throws Exception {
> 125long startTime = 
> EnvironmentEdgeManager.currentTimeMillis();
> 126if (LOGGER.isDebugEnabled()) {
> 127LOGGER.debug(LogUtil.addCustomAnnotations("Id: " + 
> scanId + ", Time: " +
> 128(EnvironmentEdgeManager.currentTimeMillis() - 
> startTime) +
> 129"ms, Scan: " + scan, 
> ScanUtil.getCustomAnnotations(scan)));
> 130}
> {code}
> The log should be placed after the {{iterator.peek}} is called.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (PHOENIX-6283) MutableIndexExtendedIT#testCompactDisabledIndex consistently fails with HBase 2.3

2020-12-30 Thread Istvan Toth (Jira)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Istvan Toth resolved PHOENIX-6283.
--
Fix Version/s: 4.16.0
   5.1.0
   Resolution: Fixed

Committed the fix to master, and added the new Test case to 4.x

Thans for the review [~vjasani]

> MutableIndexExtendedIT#testCompactDisabledIndex consistently fails with HBase 
> 2.3
> -
>
> Key: PHOENIX-6283
> URL: https://issues.apache.org/jira/browse/PHOENIX-6283
> Project: Phoenix
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.1.0
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Blocker
> Fix For: 5.1.0, 4.16.0
>
>
> This seems to be related to the Indexing rebase.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (PHOENIX-6287) Fix incorrect log in ParallelIterators.submitWork

2020-12-30 Thread chenglei (Jira)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

chenglei updated PHOENIX-6287:
--
Attachment: PHOENIX-6287-4.x.patch

> Fix incorrect log  in ParallelIterators.submitWork
> --
>
> Key: PHOENIX-6287
> URL: https://issues.apache.org/jira/browse/PHOENIX-6287
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 5.1.0, 4.16.0
>Reporter: chenglei
>Priority: Major
> Fix For: 4.16.0, 5.10
>
> Attachments: PHOENIX-6287-4.x.patch
>
>
> In {{ParallelIterators.submitWork}}, the following log is critical but is 
> meaningless:
> {code:java}
> 123@Override
> 124public PeekingResultIterator call() throws Exception {
> 125long startTime = 
> EnvironmentEdgeManager.currentTimeMillis();
> 126if (LOGGER.isDebugEnabled()) {
> 127LOGGER.debug(LogUtil.addCustomAnnotations("Id: " + 
> scanId + ", Time: " +
> 128(EnvironmentEdgeManager.currentTimeMillis() - 
> startTime) +
> 129"ms, Scan: " + scan, 
> ScanUtil.getCustomAnnotations(scan)));
> 130}
> {code}
> The log should be placed after the {{iterator.peek}} is called.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (PHOENIX-6287) Fix incorrect log in ParallelIterators.submitWork

2020-12-30 Thread chenglei (Jira)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

chenglei updated PHOENIX-6287:
--
Description: 
In {{ParallelIterators.submitWork}}, the following log is critical but is 
meaningless:
{code:java}
123@Override
124public PeekingResultIterator call() throws Exception {
125long startTime = 
EnvironmentEdgeManager.currentTimeMillis();
126if (LOGGER.isDebugEnabled()) {
127LOGGER.debug(LogUtil.addCustomAnnotations("Id: " + 
scanId + ", Time: " +
128(EnvironmentEdgeManager.currentTimeMillis() - 
startTime) +
129"ms, Scan: " + scan, 
ScanUtil.getCustomAnnotations(scan)));
130}
{code}

The log should be placed after the {{iterator.peek}} is called.

  was:In {{}}


> Fix incorrect log  in ParallelIterators.submitWork
> --
>
> Key: PHOENIX-6287
> URL: https://issues.apache.org/jira/browse/PHOENIX-6287
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 5.1.0, 4.16.0
>Reporter: chenglei
>Priority: Major
> Fix For: 4.16.0, 5.10
>
>
> In {{ParallelIterators.submitWork}}, the following log is critical but is 
> meaningless:
> {code:java}
> 123@Override
> 124public PeekingResultIterator call() throws Exception {
> 125long startTime = 
> EnvironmentEdgeManager.currentTimeMillis();
> 126if (LOGGER.isDebugEnabled()) {
> 127LOGGER.debug(LogUtil.addCustomAnnotations("Id: " + 
> scanId + ", Time: " +
> 128(EnvironmentEdgeManager.currentTimeMillis() - 
> startTime) +
> 129"ms, Scan: " + scan, 
> ScanUtil.getCustomAnnotations(scan)));
> 130}
> {code}
> The log should be placed after the {{iterator.peek}} is called.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (PHOENIX-6287) Fix incorrect log in ParallelIterators.submitWork

2020-12-30 Thread chenglei (Jira)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

chenglei updated PHOENIX-6287:
--
Description: In {{}}

> Fix incorrect log  in ParallelIterators.submitWork
> --
>
> Key: PHOENIX-6287
> URL: https://issues.apache.org/jira/browse/PHOENIX-6287
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 5.1.0, 4.16.0
>Reporter: chenglei
>Priority: Major
> Fix For: 4.16.0, 5.10
>
>
> In {{}}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (PHOENIX-6287) Fix incorrect log in ParallelIterators.submitWork

2020-12-30 Thread chenglei (Jira)
chenglei created PHOENIX-6287:
-

 Summary: Fix incorrect log  in ParallelIterators.submitWork
 Key: PHOENIX-6287
 URL: https://issues.apache.org/jira/browse/PHOENIX-6287
 Project: Phoenix
  Issue Type: Bug
Affects Versions: 5.1.0, 4.16.0
Reporter: chenglei
 Fix For: 4.16.0, 5.10






--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (PHOENIX-6272) PHOENIX-5592 introduces Dummy.java without ASF license

2020-12-30 Thread Chao Wang (Jira)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-6272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chao Wang reassigned PHOENIX-6272:
--

Assignee: Xinyi Yan  (was: Chao Wang)

> PHOENIX-5592 introduces Dummy.java without ASF license
> --
>
> Key: PHOENIX-6272
> URL: https://issues.apache.org/jira/browse/PHOENIX-6272
> Project: Phoenix
>  Issue Type: Bug
>  Components: core
>Affects Versions: master
>Reporter: Istvan Toth
>Assignee: Xinyi Yan
>Priority: Major
>
> PHOENIX-5592 introduces a Dummy.java test file.
> It contains a commented out stub that could perhaps be used as a template, 
> but more importantly it misses an ASF Header.
> If this is was committed unintentionally, it should be removed, if it thought 
> to be useful as a template and kept, then at least the proper ASF license 
> header should be added.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)