phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-886) error when drop table
Date Fri, 18 Apr 2014 08:40:18 GMT


ASF GitHub Bot commented on PHOENIX-886:

Github user karel1980 commented on the pull request:
    Concerning the additional admin call: I agree; 
    Concerning the possibility of the exception still occurreing: it is a very small window.
It should work well enough in practice. It's handled anyway so it won't cause any real harm
if it does fail (just as it doesn't do any harm right now. It's just a warning :)
    I don't really want to suppress the warning permanently, I just want to avoid the unsightly
error from sqlline in order not to confuse users. The 'WARN' level in HBase is fine (IMHO)
for other uses.
    To have HBase log the exception conditionally we would have to pass a flag from the HTable
constructor all the way down to org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.prefetchRegionCache
(unless there's a more elegant solution I didn't think of)

> error when drop table
> ---------------------
>                 Key: PHOENIX-886
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>            Reporter: yang ming
> The table can be dropped,but throw this warnning.
> 0: jdbc:phoenix:> drop table YK.VIDEO_REGION;
> 14/03/21 17:26:49 WARN client.HConnectionManager$HConnectionImplementation: Encountered
problems when prefetch META table: 
> org.apache.hadoop.hbase.TableNotFoundException: Cannot find row in .META. for table:
>         at org.apache.hadoop.hbase.client.MetaScanner.metaScan(
>         at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.prefetchRegionCache(
>         at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(
>         at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(
>         at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(
>         at org.apache.hadoop.hbase.client.HTable.finishSetup(
>         at org.apache.hadoop.hbase.client.HTable.<init>(
>         at org.apache.phoenix.query.HTableFactory$HTableFactoryImpl.getTable(
>         at org.apache.phoenix.query.ConnectionQueryServicesImpl.getTable(
>         at org.apache.phoenix.query.ConnectionQueryServicesImpl.getTableDescriptor(
>         at org.apache.phoenix.util.MetaDataUtil.hasViewIndexTable(
>         at org.apache.phoenix.schema.MetaDataClient.dropTable(
>         at org.apache.phoenix.schema.MetaDataClient.dropTable(
>         at org.apache.phoenix.jdbc.PhoenixStatement$ExecutableDropTableStatement$1.execute(
>         at org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(
>         at org.apache.phoenix.jdbc.PhoenixStatement.execute(
>         at sqlline.SqlLine$Commands.execute(
>         at sqlline.SqlLine$Commands.sql(
>         at sqlline.SqlLine.dispatch(
>         at sqlline.SqlLine.begin(
>         at sqlline.SqlLine.mainWithInputRedirection(
>         at sqlline.SqlLine.main(
> No rows affected (3.418 seconds)

This message was sent by Atlassian JIRA

View raw message