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)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
