Mailing-List: contact bigtop-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bigtop-dev@incubator.apache.org
Date: Wed, 7 Mar 2012 20:26:59 +0000 (UTC)
From: "Roman Shaposhnik (Assigned) (JIRA)" <jira@apache.org>
To: bigtop-dev@incubator.apache.org
Message-ID: 
 <243351397.35990.1331152019264.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1661076602.35987.1331152019038.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Assigned] (BIGTOP-435) need to split hadoop subpackages
 even further for hadoop-0.23
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/BIGTOP-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Shaposhnik reassigned BIGTOP-435:
---------------------------------------

    Assignee: Roman Shaposhnik
    
> need to split hadoop subpackages even further for hadoop-0.23
> -------------------------------------------------------------
>
>                 Key: BIGTOP-435
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-435
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.4.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.4.0
>
>
> Now that Hadoop 0.23 has incorporate some of the proposed changes to making the layout flexible, we no longer need the kind of hacks on which we used to rely. The proposed patch accomplishes an almost complete clean split between hadoop subpackages (treating them as independent projects) with the following 2 exceptions:
>   # libexec still need to be a common location (currently /usr/lib/hadoop/libexec)
>   # configuration files still need to be in a common location (currently /etc/hadoop/conf)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira