[
https://issues.apache.org/jira/browse/MAPREDUCE-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White updated MAPREDUCE-1033:
---------------------------------
Attachment: MAPREDUCE-1033.patch
Set of three patches (see also HADOOP-6794, MAPREDUCE-1033) to move config and
script files per previous comment.
Also:
* Fixes script permissions in HDFS and MapReduce
* Fixes a name collision in hadoop-config.sh
* Fixed hdfs-config.sh, mapred-config.sh to define HADOOP_HDFS_HOME,
HADOOP_MAPRED_HOME (respectively), which is needed to run in separate install
locations. (See also HADOOP-6342, which will make it easy to install in one
location.)
* Changes HADOOP_CORE_HOME to HADOOP_COMMON_HOME. There has been no release
with HADOOP_CORE_HOME, so it's good to make this change now.
To test, I built tarballs for each project, unpacked them in separate
locations, and successfully ran a job in pseudo-distributed mode.
> Resolve location of configuration files after project split
> -----------------------------------------------------------
>
> Key: MAPREDUCE-1033
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1033
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Affects Versions: 0.21.0
> Reporter: Vinod K V
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: MAPREDUCE-1033.patch
>
>
> At present, all the sub-projects - common, hdfs and mapreduce - have copies
> of all the configuration files. Common configuration files should be left in
> common, mapreduce specific files should be moved to mapreduce project, same
> with hdfs related files.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
