hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod K V (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-1033) Resolve location of configuration files after project split
Date Wed, 05 May 2010 03:52:04 GMT

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

Vinod K V updated MAPREDUCE-1033:
---------------------------------

    Affects Version/s: 0.21.0

Irrespective of what is going to be decided here, one thing is clear. Some of the conf files
have changed in the individual projects - I know of issues in mapreduce which changed 3-4
conf files and conf templates, by the time of this comment. We need to make sure these changes
are propagated to the right place when 0.21 is released.

> 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
>
>
> 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.


Mime
View raw message