You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Chinmay Kulkarni (Jira)" <ji...@apache.org> on 2019/12/21 00:54:09 UTC

[jira] [Closed] (PHOENIX-5178) SYSTEM schema is not getting cached at MetaData server

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

Chinmay Kulkarni closed PHOENIX-5178.
-------------------------------------

Bulk closing Jiras for the 4.15.0 release.

> 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, 5.1.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
(v8.3.4#803005)