[
https://issues.apache.org/jira/browse/HBASE-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Yates updated HBASE-6702:
-------------------------------
Description:
This was based on some discussion from HBASE-6234.
The ResourceChecker was added by N. Keywal to help resolve some hadoop qa
issues, but has since not be widely utilized. Further, with modularization we
have had to drop the ResourceChecker from the tests that are moved into the
hbase-common module because bringing the ResourceChecker up to hbase-common
would involved bringing all its dependencies (which are quite far reaching).
The question then is, what should we do with it? Get rid of it? Refactor and
resuse?
was:
The ResourceChecker was added by N. Keywal to help resolve some hadoop qa
issues, but has since not be widely utilized. Further, with modularization we
have had to drop the ResourceChecker from the tests that are moved into the
hbase-common module because bringing the ResourceChecker up to hbase-common
would involved bringing all its dependencies (which are quite far reaching).
The quest then is, what should we do with it? Get rid of it? Refactor and
resuse?
> ResourceChecker refinement
> --------------------------
>
> Key: HBASE-6702
> URL: https://issues.apache.org/jira/browse/HBASE-6702
> Project: HBase
> Issue Type: Improvement
> Components: test
> Affects Versions: 0.96.0
> Reporter: Jesse Yates
> Fix For: 0.96.0
>
>
> This was based on some discussion from HBASE-6234.
> The ResourceChecker was added by N. Keywal to help resolve some hadoop qa
> issues, but has since not be widely utilized. Further, with modularization we
> have had to drop the ResourceChecker from the tests that are moved into the
> hbase-common module because bringing the ResourceChecker up to hbase-common
> would involved bringing all its dependencies (which are quite far reaching).
> The question then is, what should we do with it? Get rid of it? Refactor and
> resuse?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
