phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-5178) SYSTEM schema is not getting cached at MetaData server
Date Tue, 12 Mar 2019 08:01:00 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-5178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16790334#comment-16790334
] 

Hudson commented on PHOENIX-5178:
---------------------------------

FAILURE: Integrated in Jenkins build Phoenix-4.x-HBase-1.4 #94 (See [https://builds.apache.org/job/Phoenix-4.x-HBase-1.4/94/])
PHOENIX-5178 SYSTEM schema is not getting cached at MetaData (ankitsinghal59: rev 9cc3529ea133b118d8272e16e0fc24301063d73f)
* (edit) phoenix-core/src/main/java/org/apache/phoenix/coprocessor/MetaDataEndpointImpl.java


> SYSTEM schema is not getting cached at MetaData server
> ------------------------------------------------------
>
>                 Key: PHOENIX-5178
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5178
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.8.0
>            Reporter: Ankit Singhal
>            Assignee: Ankit Singhal
>            Priority: Major
>             Fix For: 4.15.0
>
>         Attachments: PHOENIX-5178.patch, PHOENIX-5178_v1-addendum.patch, PHOENIX-5178_v1.patch
>
>
> During initialization, the meta connection will not be able to see the SYSTEM schema
as the scanner at meta server is running with max_timestamp of MIN_SYSTEM_TABLE_TIMESTAMP(exclusive) which
result in a new connection to create SYSTEM schema metadata everytime.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message