You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2014/02/26 01:41:22 UTC
[jira] [Updated] (PHOENIX-74) MetaDataUtil#hasViewIndexTable is
catching the wrong type of TableNotFoundException
[ https://issues.apache.org/jira/browse/PHOENIX-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Taylor updated PHOENIX-74:
--------------------------------
Based on stack trace, this must have been occurring on an older version of the code, as I don't see how this is possible:
Caused by: java.lang.RuntimeException: java.io.IOException: org.apache.hadoop.hbase.TableNotFoundException: _IDX_USER_SESSION
at org.apache.phoenix.query.ConnectionQueryServicesImpl.getTable(ConnectionQueryServicesImpl.java:187)
at org.apache.phoenix.query.ConnectionQueryServicesImpl.getTableDescriptor(ConnectionQueryServicesImpl.java:194)
at org.apache.phoenix.util.MetaDataUtil.hasViewIndexTable(MetaDataUtil.java:285)
at org.apache.phoenix.schema.MetaDataClient.dropTable(MetaDataClient.java:1252)
at org.apache.phoenix.schema.MetaDataClient.dropTable(MetaDataClient.java:1195)
at org.apache.phoenix.jdbc.PhoenixStatement$ExecutableDropTableStatement$1.execute(PhoenixStatement.java:515)
at org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:224)
at org.apache.phoenix.jdbc.PhoenixStatement.execute(PhoenixStatement.java:875)
at system.security.session.DataInHbaseSessionEncoder.<clinit>(DataInHbaseSessionEncoder.java:49)
... 33 more
Caused by: java.io.IOException: org.apache.hadoop.hbase.TableNotFoundException: _IDX_USER_SESSION
at hbase.client.ProtectedHTableFactory.createHTable(ProtectedHTableFactory.java:382)
at hbase.client.ProtectedHTableFactory.getProtectedHTable(ProtectedHTableFactory.java:175)
at org.apache.phoenix.query.SfdcHTableFactory.getTable(SfdcHTableFactory.java:39)
at org.apache.phoenix.query.ConnectionQueryServicesImpl.getTable(ConnectionQueryServicesImpl.java:181)
... 41 more
Caused by: org.apache.hadoop.hbase.TableNotFoundException: _IDX_USER_SESSION
at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:1036)
at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:898)
at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:855)
at org.apache.hadoop.hbase.client.HTable.finishSetup(HTable.java:233)
at org.apache.hadoop.hbase.client.HTable.<init>(HTable.java:225)
at hbase.client.ProtectedHTableFactory.createHTable(ProtectedHTableFactory.java:360)
... 44 more
> MetaDataUtil#hasViewIndexTable is catching the wrong type of TableNotFoundException
> -----------------------------------------------------------------------------------
>
> Key: PHOENIX-74
> URL: https://issues.apache.org/jira/browse/PHOENIX-74
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Samarth
> Assignee: James Taylor
>
> MetadaUtil#hasViewIndexTable is catching org.apache.phoenix.schema.TableNotFoundException instead of org.apache.hadoop.hbase which is what is being thrown by the code inside the try block. As a result, the exception gets bubbled up and the return false inside the catch doesn't executed (when the table name doesn't exist).
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)