[
https://issues.apache.org/jira/browse/HBASE-6411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418517#comment-13418517
]
Elliott Clark commented on HBASE-6411:
--------------------------------------
bq.At the same time, by adding extra abstraction hadoop-compat with
hadoop1/2-compat modules in this case turn into smth like metrics-api and
metrics-impl modules. I.e. not just "shim over hadoop classes". Which may be
OK, I don't know.
Yes. That's what I was thinking. That's also why one of the work items is to
start using guice to inject dependencies. However I am hoping that more than
just metrics will be abstracted over. Right now we have issues with compiling
for hadoop1 and running with hadoop2. I'm hoping that can be solved in the
same way that we've solved metrics2 issues.
As things are modularized it gives us an opportunity make things more
abstracted and maybe make it so that hbase's usage of hadoop is fully
pluggable. This would make testing things easier and it could allow us to have
other storage engines. (obviously that's a long way away and might not ever be
realized, however just trying means that things become more testable.)
> Move Master Metrics to metrics 2
> --------------------------------
>
> Key: HBASE-6411
> URL: https://issues.apache.org/jira/browse/HBASE-6411
> Project: HBase
> Issue Type: Sub-task
> Reporter: Elliott Clark
> Assignee: Alex Baranau
> Attachments: HBASE-6411_concept.patch
>
>
> Move Master Metrics to metrics 2
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
