Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of harsh@cloudera.com designates
 209.85.223.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <520445E0.30609@gmail.com>
References: 
 <CAHYL6kFBEvzMWxN7NucvH8qTGO0mpn_E8rA-62yWj4Fqy9MvQA@mail.gmail.com>
 <520445E0.30609@gmail.com>
From: Harsh J <harsh@cloudera.com>
Date: Fri, 9 Aug 2013 08:00:45 +0530
Message-ID: 
 <CAOcnVr1ZosmGxE-674pPng1BhbU_TvPpEHLuaWEX8PMiYmCJjQ@mail.gmail.com>
Subject: Re: alternative to $HADOOP_HOME/lib
To: "<user@hadoop.apache.org>" <user@hadoop.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

John,

I assume you do not wish to be using the DistributedCache (or a HDFS
location for DistributedCache), which is the most ideal way to ship
jars.

You can place your jars onto the TT classpaths by placing them at an
arbitrary location such as /opt/jars, and editing the TT's
hadoop-env.sh to extend HADOOP_CLASSPATH to include this extra
location. This would still require administrative configuration edits,
and service restarts each time you want to add a new jar or change a
jar. With DC, these aren't required.

On Fri, Aug 9, 2013 at 6:59 AM, Sanjeev Verma <sanjeev.x.verma@gmail.com> wrote:
> On 08/08/2013 09:23 PM, John Hancock wrote:
>>
>> Where else might one put .jar files that a map/reduce job will need?
>
> Why do you need an alternative location? Is there a constraint on being able
> to place your library jars under $HADOOP_HOME/lib?


-- 
Harsh J