hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-2550) bin/mapred no longer works from a source checkout
Date Thu, 16 Jun 2011 17:31:47 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050576#comment-13050576

Todd Lipcon commented on MAPREDUCE-2550:

Sorry for slow response, I missed this in my jira box.

Eric: my point is that the next thing after "export HADOOP_PREFIX=..." is to source hadoop-config.sh
(wherever it might be found). The first export in that file is to export HADOOP_PREFIX again.
So regardless of whether this is a dev env or installed env, the export in mapred-config.sh
should be redundant, no?

> bin/mapred no longer works from a source checkout
> -------------------------------------------------
>                 Key: MAPREDUCE-2550
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2550
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.20.3
>         Environment: Java 6, Redhat 5.5
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>            Priority: Blocker
>             Fix For: 0.20.3
>         Attachments: MAPREDUCE-2550-1.patch, MAPREDUCE-2550.patch
> Developer may want to run hadoop without extracting tarball.  It would be nice if existing
method to run mapred scripts from source code is preserved for developers.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message