James

We’re on Phoenix 4.2 on HDP 2.2.6.

I’ve tried reproducing the problem and I can’t. My issue is specific to these 
two tables. When I try recreating the exact same table I can drop it. I’m 
willing to do some digging on these tables if it will help you, but in the end 
what I’d like to do is get them dropped.

Michael McAllister
Staff Data Warehouse Engineer | Decision Systems
[email protected]<mailto:[email protected]> | C: 512.423.7447 | 
skype: michael.mcallister.ha<mailto:[email protected]> | webex: 
https://h.a/mikewebex

[cid:[email protected]]
This electronic communication (including any attachment) is confidential.  If 
you are not an intended recipient of this communication, please be advised that 
any disclosure, dissemination, distribution, copying or other use of this 
communication or any attachment is strictly prohibited.  If you have received 
this communication in error, please notify the sender immediately by reply 
e-mail and promptly destroy all electronic and printed copies of this 
communication and any attachment.

On Aug 24, 2015, at 10:48 PM, James Taylor 
<[email protected]<mailto:[email protected]>> wrote:

Hi Michael,
What version are you on over there? Can you setup a test that consistently 
reproduces the issue?
Thanks,
James

On Mon, Aug 24, 2015 at 8:20 PM, Michael McAllister 
<[email protected]<mailto:[email protected]>> wrote:
Hi

I have an empty table that, when I try and drop, I get an error returned.

I issue a command similar to the following:-

drop table myschema.mytable;

I get the following error:-

 22:17:53  [DROP - 0 row(s), 0.276 secs]  [Error Code: 101, SQL State: 08000]  
org.apache.hadoop.hbase.DoNotRetryIOException: MYSCHEMA.MYTABLE: 29
at org.apache.phoenix.util.ServerUtil.createIOException(ServerUtil.java:84)
at 
org.apache.phoenix.coprocessor.MetaDataEndpointImpl.dropTable(MetaDataEndpointImpl.java:965)
at 
org.apache.phoenix.coprocessor.generated.MetaDataProtos$MetaDataService.callMethod(MetaDataProtos.java:7768)
at org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:6896)
at 
org.apache.hadoop.hbase.regionserver.HRegionServer.execServiceOnRegion(HRegionServer.java:3420)
at 
org.apache.hadoop.hbase.regionserver.HRegionServer.execService(HRegionServer.java:3402)
at 
org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:29998)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2078)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
at org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.ArrayIndexOutOfBoundsException: 29
at org.apache.phoenix.schema.PTableImpl.init(PTableImpl.java:320)
at org.apache.phoenix.schema.PTableImpl.<init>(PTableImpl.java:250)
at org.apache.phoenix.schema.PTableImpl.makePTable(PTableImpl.java:240)
at 
org.apache.phoenix.coprocessor.MetaDataEndpointImpl.getTable(MetaDataEndpointImpl.java:638)
at 
org.apache.phoenix.coprocessor.MetaDataEndpointImpl.buildTable(MetaDataEndpointImpl.java:376)
at 
org.apache.phoenix.coprocessor.MetaDataEndpointImpl.doDropTable(MetaDataEndpointImpl.java:985)
at 
org.apache.phoenix.coprocessor.MetaDataEndpointImpl.dropTable(MetaDataEndpointImpl.java:939)
... 10 more
... 1 statement(s) executed, 0 row(s) affected, exec/fetch time: 0.276/0.000 
sec  [0 successful, 0 warnings, 1 errors]


Michael McAllister
Staff Data Warehouse Engineer | Decision Systems
[email protected]<mailto:[email protected]> | C: 
512.423.7447<tel:512.423.7447> | skype: 
michael.mcallister.ha<mailto:[email protected]> | webex: 
https://h.a/mikewebex

<image002.png>
This electronic communication (including any attachment) is confidential.  If 
you are not an intended recipient of this communication, please be advised that 
any disclosure, dissemination, distribution, copying or other use of this 
communication or any attachment is strictly prohibited.  If you have received 
this communication in error, please notify the sender immediately by reply 
e-mail and promptly destroy all electronic and printed copies of this 
communication and any attachment.



Reply via email to