Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4ACF3EED4 for ; Tue, 15 Jan 2013 18:48:10 +0000 (UTC) Received: (qmail 59191 invoked by uid 500); 15 Jan 2013 18:48:05 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 59087 invoked by uid 500); 15 Jan 2013 18:48:05 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 59080 invoked by uid 99); 15 Jan 2013 18:48:05 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Jan 2013 18:48:05 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jayunit100@gmail.com designates 209.85.220.171 as permitted sender) Received: from [209.85.220.171] (HELO mail-vc0-f171.google.com) (209.85.220.171) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Jan 2013 18:47:58 +0000 Received: by mail-vc0-f171.google.com with SMTP id n11so465408vch.16 for ; Tue, 15 Jan 2013 10:47:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=MHwXZqs6Y3hymllSduXlkVm/rej/OtcoHC8CXq3ng4U=; b=udywEI+FmEEStMJV66Pfn5w7z1dmVNw6sOLYNJNuqC6teZnHAmqIKrAfxElKXq4DlW i0fTE575GWxnpGPDtjx+xMW3BtwwPc9obnQEwI7RsY6yQ44qj6IU8MYDwXKB2LU7p4Vm idOp6VE5Vg+wau7xo2cFK5dpC1PkMRNW0gdnwrE7FCkhOrUqTebLLJx47qZJm8NcWxcW o4B0UHsHxw4jdnNmugtluQWIRWNlflT/hbN6zyK3pLxPZbalWsaHofhQMpDlKh0z4eH6 lrAqXBPXIR+Vw4IODcZXOpZMH7udkHKki777q4ro4gxbUwvlk/+HvdEHiXAT1aIX1JtF i3PA== MIME-Version: 1.0 Received: by 10.220.239.143 with SMTP id kw15mr104148140vcb.62.1358275657843; Tue, 15 Jan 2013 10:47:37 -0800 (PST) Received: by 10.58.46.68 with HTTP; Tue, 15 Jan 2013 10:47:37 -0800 (PST) In-Reply-To: References: Date: Tue, 15 Jan 2013 13:47:37 -0500 Message-ID: Subject: Re: FileSystem.workingDir vs mapred.local.dir From: Jay Vyas To: "common-user@hadoop.apache.org" Content-Type: multipart/alternative; boundary=14dae9ccd4ee17c54004d35832be X-Virus-Checked: Checked by ClamAV on apache.org --14dae9ccd4ee17c54004d35832be Content-Type: text/plain; charset=ISO-8859-1 what do you mean by "workingdir for a filesystem" ? I never thought that a fileSystem should need or have a special workingDir ? On Tue, Jan 15, 2013 at 12:43 PM, Hemanth Yamijala < yhemanth@thoughtworks.com> wrote: > Hi, > > AFAIK, the mapred.local.dir property refers to a set of directories under > which different types of data related to mapreduce jobs are stored - for > e.g. intermediate data, localized files for a job etc. The working > directory for a mapreduce job is configured under a sub directory within > one of the directories configured in this property. > > The workingDir property of the FileSystem class simply seems to indicate > the working directory for a given filesystem as set by applications. > > They don't seem very related per se, unless I am missing something ? > > Thanks > Hemanth > > > On Tue, Jan 15, 2013 at 2:54 AM, Jay Vyas wrote: > >> Hi guys: What is the relationship between the "working directory" in the >> FileSystem class (filesystem.workingDir), compared with the >> mapred.local.dir properties ? >> >> It seems like these would essentially refer to the same thing? >> -- >> Jay Vyas >> http://jayunit100.blogspot.com >> > > -- Jay Vyas http://jayunit100.blogspot.com --14dae9ccd4ee17c54004d35832be Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
what do you mean by "workingdir for a filesystem"= ; ?=A0 I never thought that a fileSystem should
need or have a special = workingDir ?=A0


On Tue, Jan 15, 2013 at 12:43 PM, Hemanth Yamijala <yhemanth@thoug= htworks.com> wrote:
Hi,

AFAIK, the mapred.local.dir property refers to a set= of directories under which different types of data related to mapreduce jo= bs are stored - for e.g. intermediate data, localized files for a job etc. = The working directory for a mapreduce job is configured under a sub directo= ry within one of the directories configured in this property.

The workingDir property of the Fi= leSystem class simply seems to indicate the working directory for a given f= ilesystem as set by applications.

They don't seem very related per se, unless = I am missing something ?

Thanks
Hemanth


On Tue, Jan 15, 2013 at 2:54 AM, Jay Vyas <jayunit100@gmail.com>= wrote:
Hi guys:=A0 What is the rel= ationship between the "working directory" in the FileSystem class= (filesystem.workingDir), compared with the mapred.local.dir properties ?

It seems like these would essentially refer to the same thing?
--
Jay Vyas
http://jayunit100.blogspot.com




--
Jay Vyas
http://jayunit100.blogspo= t.com --14dae9ccd4ee17c54004d35832be--