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

Vincent Poon commented on PHOENIX-5103:
---------------------------------------

If I try to connect a 4.15 client afterwards, it's unable to upgrade:

19/01/18 16:20:45 WARN query.ConnectionQueryServicesImpl: Successfully restored 
SYSTEM:CATALOG using snapshot 
SNAPSHOT_SYSTEM.CATALOG_4.14.x_TO_4.15.0_20190118162042
19/01/18 16:20:49 WARN query.ConnectionQueryServicesImpl: Successfully restored 
and enabled SYSTEM:CATALOG using snapshot 
SNAPSHOT_SYSTEM.CATALOG_4.14.x_TO_4.15.0_20190118162042
Error: ERROR 1012 (42M03): Table undefined. tableName=SYSTEM.CHILD_LINK 
(state=42M03,code=1012)
org.apache.phoenix.schema.TableNotFoundException: ERROR 1012 (42M03): Table 
undefined. tableName=SYSTEM.CHILD_LINK

> Can't create/drop table using 4.14 client against 4.15 server
> -------------------------------------------------------------
>
>                 Key: PHOENIX-5103
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5103
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.15.0
>            Reporter: Vincent Poon
>            Priority: Major
>
> server is running 4.15 commit e3280f
> Connect with 4.14.1 client.  Create table gives this:
> Caused by: 
> org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.TableNotFoundException):
>  org.apache.hadoop.hbase.TableNotFoundException: Table 'SYSTEM:CHILD_LINK' 
> was not found, got: SYSTEM:CATALOG.
>       at 
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegionInMeta(ConnectionManager.java:1362)
>       at 
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(ConnectionManager.java:1230)
>       at 
> org.apache.hadoop.hbase.client.CoprocessorHConnection.locateRegion(CoprocessorHConnection.java:41)



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

Reply via email to