phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas D'Silva (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-3870) Backward compatibility fails between v4.9.0 and head of 4.x (4.11-SNAPSHOT)
Date Fri, 26 May 2017 21:37:04 GMT


Thomas D'Silva commented on PHOENIX-3870:

This is failing because even though the server jar is 4.11, SYSTEM.CATALOG has not yet been
upgraded to 4.11, so the PARENT->CHILD view links are missing. When we drop the base table,
we check to see if there are any child views (by searching for PARENT->CHILD links) and
don't find any, so we allow the table to be dropped (instead of throwing an exception since
the drop table statement didn't include CASCADE). 
If SYSTEM.CATALOG has not yet been upgraded we should find the child views using the CHILD->PARENT
[~jamestaylor] Whats the best way to figure out the version of SYSTEM.CATALOG ?  Should I
load the PTable and lookup the timestamp? 

FYI [~churromorales] 

> Backward compatibility fails between v4.9.0 and head of 4.x (4.11-SNAPSHOT)
> ---------------------------------------------------------------------------
>                 Key: PHOENIX-3870
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Mujtaba Chohan
>            Assignee: Thomas D'Silva
> {noformat}
> Caused by: org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(org.apache.hadoop.hbase.DoNotRetryIOException):
org.apache.hadoop.hbase.DoNotRetryIOException: SCH.MYDELETE: Didn't find expected key values
for table row in metadata row
> 	at org.apache.phoenix.util.ServerUtil.createIOException(
> 	at org.apache.phoenix.coprocessor.MetaDataEndpointImpl.createTable(
> 	at org.apache.phoenix.coprocessor.generated.MetaDataProtos$MetaDataService.callMethod(
> 	at org.apache.hadoop.hbase.regionserver.HRegion.execService(
> 	at org.apache.hadoop.hbase.regionserver.HRegionServer.execServiceOnRegion(
> 	at org.apache.hadoop.hbase.regionserver.HRegionServer.execService(
> 	at org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(
> 	at
> 	at
> 	at org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(
> 	at org.apache.hadoop.hbase.ipc.RpcExecutor$
> 	at
> Caused by: java.lang.IllegalStateException: Didn't find expected key values for table
row in metadata row
> 	at org.apache.phoenix.coprocessor.MetaDataEndpointImpl.getTable(
> 	at org.apache.phoenix.coprocessor.MetaDataEndpointImpl.buildTable(
> 	at org.apache.phoenix.coprocessor.MetaDataEndpointImpl.loadTable(
> 	at org.apache.phoenix.coprocessor.MetaDataEndpointImpl.createTable(
> {noformat}
> Steps
> * Create and drop table with 4.9 client/4.x server
> {{create table sch.mydelete (pk1 varchar not null primary key, mycol varchar) salt_buckets=4;
drop table sch.mydelete;}}
> * Exception on creating table again with 4.x client/server.

This message was sent by Atlassian JIRA

View raw message