Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <514300472.644211270160067279.JavaMail.jira@brutus.apache.org>
Date: Thu, 1 Apr 2010 22:14:27 +0000 (UTC)
From: "Allen Wittenauer (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Resolved: (MAPREDUCE-1666) job output chroot support
In-Reply-To: <1019566008.642391270154607508.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Allen Wittenauer resolved MAPREDUCE-1666.
-----------------------------------------

    Resolution: Invalid

Muhaha!  I'm quite stunned to see I'm held in such high regard!
 
Anyway, I've been told to close this out, as the people who really wanted to do this say this will work.

Thanks.

> job output chroot support
> -------------------------
>
>                 Key: MAPREDUCE-1666
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1666
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>          Components: job submission
>    Affects Versions: 0.20.2
>            Reporter: Allen Wittenauer
>            Priority: Minor
>
> It would be useful to be able to submit the same job and have it chroot the output to a different base directory before execution.  This would allow for input to be the same, but output different for the same job over multiple runs (potentially by different users).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.