[
https://issues.apache.org/jira/browse/HBASE-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621623#action_12621623
]
stack commented on HBASE-729:
-----------------------------
Ignore my comment in above.
Cleaning and retrying all passed (just takes a while).
> client region/metadata cache should have a public method for invalidating
> entries
> ---------------------------------------------------------------------------------
>
> Key: HBASE-729
> URL: https://issues.apache.org/jira/browse/HBASE-729
> Project: Hadoop HBase
> Issue Type: Bug
> Components: client
> Affects Versions: 0.2.0
> Environment: Linux CentOS 5.1 x86_64 / JDK 1.6
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Priority: Minor
> Attachments: 729.patch
>
>
> While writing a testcase for HBASE-62, I observed that table metadata is
> cached as part of the region information cached client side. This cached
> region information (and therefore table metadata) is not directly invalidated
> by disable/enable table, so to get up to date metadata the client may have to
> use a scanner over .META. directly using the meta visitor. Ideally other
> client code -- for example the support for HBASE-62 -- should be able to
> invalidate entries as necessary, so then the next HTable.getTableDescriptor()
> would go to meta to return up to date information instead of incorrectly
> reusing outdated information from the cache.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
