[
https://issues.apache.org/jira/browse/HBASE-13525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505782#comment-14505782
]
Allen Wittenauer commented on HBASE-13525:
------------------------------------------
One of my unstated goals with HADOOP-11746 was for it to be a mostly drop-in
replacement for any project currently using the older bits. (A quick pass
through most of the ecosystem reveals that the majority are using some form of
it or another). The plug-in capabilities certainly make it easier to add
custom stuff, but it's a lot harder to fix some assumptions made about the
source tree layout and maven usage (of course).
(Weirdly, this is the second time that having some generic bits that the entire
ecosystem could leverage has come up with some major rewrite I've undertaken.
Roman suggested pulling the base shell scripts out of Hadoop and forming a
completely separate project!)
Anyway, for better or worse, HBase probably has the most customized out of all
of them, based upon my quick pass through. I'll try to offer guidance where I
can. It'll be interesting to see what does/doesn't work, especially with the
new framework. The biggest one I'm worried about are the backward compatibility
bits. I *hope* override works there, but I haven't had a chance to actually
test that part.... ;)
> Update test-patch to leverage rewrite in Hadoop
> -----------------------------------------------
>
> Key: HBASE-13525
> URL: https://issues.apache.org/jira/browse/HBASE-13525
> Project: HBase
> Issue Type: Improvement
> Components: build
> Reporter: Sean Busbey
> Labels: jenkins
> Fix For: 2.0.0
>
>
> Once HADOOP-11746 lands over in Hadoop, incorporate its changes into our
> test-patch. Most likely easiest approach is to start with the Hadoop version
> and add in the features we have locally that they don't.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
