accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-2126) Hadoop profile names should be consistent across branches
Date Sat, 04 Jan 2014 02:48:51 GMT


Christopher Tubbs commented on ACCUMULO-2126:

[~mdrob]: the version of ZK is independent of Hadoop. Also, as stated in the comment in the
POM, we depend on 3.3.x (latest, bugfix) even though 3.4.x works fine, to ensure we have max
compatibility (we don't really *need* 3.4.x features). With ZooKeeper, this is much more manageable,
because they're better at API stability than Hadoop.

> Hadoop profile names should be consistent across branches
> ---------------------------------------------------------
>                 Key: ACCUMULO-2126
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: build
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Minor
>             Fix For: 1.4.5, 1.5.1, 1.6.0
>         Attachments: ACCUMULO-2126.1-1.5.1-SNAPSHOT.patch.txt, ACCUMULO-2126.1-1.6.0-SNAPSHOT.patch.txt,
> ACCUMULO-1419 changed the hadoop pofile names to reflect the major components used. This
makes documenting how to build against a major hadoop line across all of our branches more
difficult than necessary.
> Since the changes in what we need to do vary with the Hadoop line, e.g. Hadoop 1 and
Hadoop 2, we should name them appropriately.
> Additionally, our current activation scheme for hte default doesn't allow activating
it by name.

This message was sent by Atlassian JIRA

View raw message