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

ASF GitHub Bot commented on PHOENIX-886:
----------------------------------------

Github user karel1980 commented on the pull request:

    https://github.com/apache/incubator-phoenix/pull/29#issuecomment-40795390
  
    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: https://issues.apache.org/jira/browse/PHOENIX-886
>             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:10.10.69.117> 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: _IDX_YK.VIDEO_REGION, row=_IDX_YK.VIDEO_REGION,,99999999999999
>         at 
> org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:151)
>         at 
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.prefetchRegionCache(HConnectionManager.java:1059)
>         at 
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:1121)
>         at 
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:1001)
>         at 
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:958)
>         at org.apache.hadoop.hbase.client.HTable.finishSetup(HTable.java:251)
>         at org.apache.hadoop.hbase.client.HTable.<init>(HTable.java:243)
>         at 
> org.apache.phoenix.query.HTableFactory$HTableFactoryImpl.getTable(HTableFactory.java:51)
>         at 
> org.apache.phoenix.query.ConnectionQueryServicesImpl.getTable(ConnectionQueryServicesImpl.java:242)
>         at 
> org.apache.phoenix.query.ConnectionQueryServicesImpl.getTableDescriptor(ConnectionQueryServicesImpl.java:254)
>         at 
> org.apache.phoenix.util.MetaDataUtil.hasViewIndexTable(MetaDataUtil.java:269)
>         at 
> org.apache.phoenix.schema.MetaDataClient.dropTable(MetaDataClient.java:1303)
>         at 
> org.apache.phoenix.schema.MetaDataClient.dropTable(MetaDataClient.java:1244)
>         at 
> org.apache.phoenix.jdbc.PhoenixStatement$ExecutableDropTableStatement$1.execute(PhoenixStatement.java:519)
>         at 
> org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement.java:226)
>         at 
> org.apache.phoenix.jdbc.PhoenixStatement.execute(PhoenixStatement.java:919)
>         at sqlline.SqlLine$Commands.execute(SqlLine.java:3673)
>         at sqlline.SqlLine$Commands.sql(SqlLine.java:3584)
>         at sqlline.SqlLine.dispatch(SqlLine.java:821)
>         at sqlline.SqlLine.begin(SqlLine.java:699)
>         at sqlline.SqlLine.mainWithInputRedirection(SqlLine.java:441)
>         at sqlline.SqlLine.main(SqlLine.java:424)
> No rows affected (3.418 seconds)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to