[
https://issues.apache.org/jira/browse/HBASE-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046828#comment-13046828
]
stack commented on HBASE-2233:
------------------------------
OK. Did a bit more testing first. There may be some tests that need
addressing if hadoop 0.22 is under hbase. I think I got them all.
TestHSplitLog was the last one I was working on; it seemed to have failing unit
tests but coming back to it, they pass now (TestHFileOutputFormat does not
pass, not w/o reverting the avro version to that of hadoop 0.22). Will create
new issues for tests that fail against hadoop 0.22. Committed to TRUNK
Thanks for review Todd.
As said above we do not work against hadoop 0.21, not w/o backport of
"HADOOP-7351 Regression: HttpServer#getWebAppsPath used to be protected so
subclasses could supply alternate webapps path but it was made private by
HADOOP-6461" and "HDFS-1948 Forward port 'hdfs-1520 lightweight namenode
operation to trigger lease recovery'"
> Support both Hadoop 0.20, 0.21, and 0.22
> ----------------------------------------
>
> Key: HBASE-2233
> URL: https://issues.apache.org/jira/browse/HBASE-2233
> Project: HBase
> Issue Type: New Feature
> Reporter: Jean-Daniel Cryans
> Assignee: stack
> Priority: Critical
> Fix For: 0.92.0
>
> Attachments: 2233-v2.txt, 2233-v3.txt, 2233-v4.txt, 2233-v5.txt,
> 2233.txt, pom.to.go.against.hadoop.trunk.txt
>
>
> Since Hadoop 0.21 isn't going to be well supported and that a lot of users
> may wish to stick on 0.20, the next HBase major release should support both
> 0.20 and 0.21.
> HDFS-265 support will be swapped for HDFS-200 if running on HDFS 0.20. A
> cluster without that patchset shouldn't be supported.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
