[jira] [Updated] (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 ] Thomas D'Silva updated PHOENIX-5178: Fix Version/s: 5.1.0 > 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 (v7.6.3#76005)
[jira] [Updated] (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 ] Ankit Singhal updated PHOENIX-5178: --- Attachment: PHOENIX-5178_v1-addendum.patch > 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)
[jira] [Updated] (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 ] Ankit Singhal updated PHOENIX-5178: --- Attachment: PHOENIX-5178_v1.patch > 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 > Attachments: PHOENIX-5178.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)
[jira] [Updated] (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 ] Ankit Singhal updated PHOENIX-5178: --- Attachment: PHOENIX-5178.patch > 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 > Attachments: PHOENIX-5178.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)
