[
https://issues.apache.org/jira/browse/ACCUMULO-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13834127#comment-13834127
]
Christopher Tubbs commented on ACCUMULO-1793:
---------------------------------------------
[~fwiffo] wrote:
{quote}I always viewed the default version (and profile) to represent the
lowest version that we're maintaining compatability with.{quote}
That's kind of what we've been doing with ZooKeeper (we've been sticking to the
latest bugfix release of the 3.3 line, rather than jump to 3.4, so we don't
accidentally use a new feature that breaks compatibility), and this makes
complete sense when you're dealing with an application, like ZooKeeper, that is
very rigid about being long-term backwards-compatible. I'm not sure Hadoop can
be considered such an application (Accumulo certainly isn't... yet).
The best thing, in this regard, is probably to document and test against the
range of supported versions, and not to change that range of supported versions
on a minor/bugfix release.... regardless of what the POM says.
> 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)
