[
https://issues.apache.org/jira/browse/ACCUMULO-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13833469#comment-13833469
]
Sean Busbey commented on ACCUMULO-1793:
---------------------------------------
[~elserj], Hadoop 0.20 is part of the Hadoop 1.0 line. Since our examples in
the README showed building against 0.23 by specifying the hadoop 2 profile and
the version (and 0.23 is part of the Hadoop 2 lineage), it didn't seem odd me
to have 1.4.x default the Hadoop 1 line to 0.20. But I'm pretty used to Hadoop
versions being terrible at this point.
The binaries built against 0.20.203.0 should be binary compatible with the
Hadoop 1.x releases, but should not be binary compatible with the 2.x releases.
Similarly, the binaries built against 2.2.0 won't be compatible with Hadoop 1.x
releases (including 0.20.203.0). Unless we backport (or create) some fancy shim
work under ACCUMULO-1796.
Which part feels glued on? Having a third profile? Since 0.20 is a Hadoop 1
version, I'm not sure that we need to. If it makes the insanity of Hadoop
versions easier to follow, I don't think it hurts. We could just change the
name of the Hadoop 1 profile to Hadoop-0.20 and not have 1.4 speak to 1.x.
As an aside, I think the patch would be better suited to ACCUMULO-1795 since
that's the ticket that deals with building against 0.20.203 and non-Hadoop 2
compat.
> Update Hadoop 2.0 profile to Hadoop 2.2.0
> -----------------------------------------
>
> Key: ACCUMULO-1793
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1793
> Project: Accumulo
> Issue Type: Sub-task
> Affects Versions: 1.4.4, 1.5.0
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Attachments:
> 0001-ACCUMULO-1793-Changes-that-to-make-semi-sane-build-p.patch,
> ACCUMULO-1793.1.patch.txt
>
>
> now that Hadoop 2 has a GA release, update the Hadoop 2.0 profile to target
> it.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
