[
https://issues.apache.org/jira/browse/PHOENIX-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16890861#comment-16890861
]
Hadoop QA commented on PHOENIX-5403:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12975465/PHOENIX-5403.patch
against master branch at commit 62387ee3c55f8be1947161bc9d501b1867cc24f1.
ATTACHMENT ID: 12975465
{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:
org.apache.phoenix.compile.QueryCompilerTest
Test results:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/2828//testReport/
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/2828//console
This message is automatically generated.
> Optimize metadata cache lookup of global tables using a tenant specific
> connection
> ----------------------------------------------------------------------------------
>
> Key: PHOENIX-5403
> URL: https://issues.apache.org/jira/browse/PHOENIX-5403
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.14.2
> Reporter: Thomas D'Silva
> Assignee: Chinmay Kulkarni
> Priority: Major
> Fix For: 4.15.0, 5.1.0
>
> Attachments: PHOENIX-5403.patch, diff.patch
>
>
> If we use a teanant specific connection to look up a global table we always
> make an rpc to the server even if the UPDATE_CACHE_FREQUENCY is set on the
> table.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
