[
https://issues.apache.org/jira/browse/PHOENIX-5655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17007411#comment-17007411
]
Hadoop QA commented on PHOENIX-5655:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12989862/PHOENIX-5655.master.002.patch
against master branch at commit 356f4cd7d43bccb9538a5a2b94863b1c52cd9aad.
ATTACHMENT ID: 12989862
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:red}-1 core tests{color}. The patch failed these unit tests:
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.PermissionNSEnabledIT
Test results:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/3228//testReport/
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/3228//console
This message is automatically generated.
> ServerCache using table map is not correctly removed
> ----------------------------------------------------
>
> Key: PHOENIX-5655
> URL: https://issues.apache.org/jira/browse/PHOENIX-5655
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.1.0
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Major
> Fix For: 5.1.0, 4.15.1
>
> Attachments: PHOENIX-5655.master.000.patch,
> PHOENIX-5655.master.002.patch
>
>
> ServerCacheClient should remove cacheId -> PTable map entry while removing
> cached table from all RegionServers, which is not happening correctly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
