You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Vinod K V (JIRA)" <ji...@apache.org> on 2009/09/24 10:04:16 UTC
[jira] Created: (MAPREDUCE-1033) Resolve location of configuration
files after project split
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
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.
[jira] Updated: (MAPREDUCE-1033) Resolve location of configuration
files after project split
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated MAPREDUCE-1033:
---------------------------------
Status: Patch Available (was: Open)
> 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
> Assignee: Tom White
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: MAPREDUCE-1033.patch, MAPREDUCE-1033.patch, 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.
[jira] Updated: (MAPREDUCE-1033) Resolve location of configuration
files after project split
Posted by "Vinod K V (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (MAPREDUCE-1033) Resolve location of scripts and
configuration files after project split
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877323#action_12877323 ]
Hadoop QA commented on MAPREDUCE-1033:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12446106/MAPREDUCE-1033.patch
against trunk revision 950286.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 2 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed core unit tests.
-1 contrib tests. The patch failed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/220/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/220/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/220/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/220/console
This message is automatically generated.
> Resolve location of scripts and 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
> Assignee: Tom White
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: MAPREDUCE-1033.patch, MAPREDUCE-1033.patch, MAPREDUCE-1033.patch, 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.
[jira] Updated: (MAPREDUCE-1033) Resolve location of configuration
files after project split
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated MAPREDUCE-1033:
---------------------------------
Status: Open (was: Patch Available)
> 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
> Assignee: Tom White
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: MAPREDUCE-1033.patch, MAPREDUCE-1033.patch, 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.
[jira] Updated: (MAPREDUCE-1033) Resolve location of configuration
files after project split
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (MAPREDUCE-1033) Resolve location of
configuration files after project split
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12873864#action_12873864 ]
Hadoop QA commented on MAPREDUCE-1033:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12445967/MAPREDUCE-1033.patch
against trunk revision 949815.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 2 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/213/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/213/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/213/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/213/console
This message is automatically generated.
> 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
> Assignee: Tom White
> 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.
[jira] Updated: (MAPREDUCE-1033) Resolve location of scripts and
configuration files after project split
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ 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
> Resolve location of scripts and 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
> Assignee: Tom White
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: MAPREDUCE-1033.patch, MAPREDUCE-1033.patch, MAPREDUCE-1033.patch, 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.
[jira] Commented: (MAPREDUCE-1033) Resolve location of
configuration files after project split
Posted by "Vinod K V (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864136#action_12864136 ]
Vinod K V commented on MAPREDUCE-1033:
--------------------------------------
Tom and Owen, I took the liberty of adding you guys to the watch list so that this issue can move forward..
> 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.
[jira] Commented: (MAPREDUCE-1033) Resolve location of scripts and
configuration files after project split
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12879096#action_12879096 ]
Hudson commented on MAPREDUCE-1033:
-----------------------------------
Integrated in Hadoop-Hdfs-trunk-Commit #310 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Hdfs-trunk-Commit/310/])
> Resolve location of scripts and 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
> Assignee: Tom White
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: MAPREDUCE-1033.patch, MAPREDUCE-1033.patch, MAPREDUCE-1033.patch, 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.
[jira] Commented: (MAPREDUCE-1033) Resolve location of
configuration files after project split
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864892#action_12864892 ]
Tom White commented on MAPREDUCE-1033:
--------------------------------------
Files that should be in mapreduce/conf
{noformat}
capacity-scheduler.xml
capacity-scheduler.xml.template
fair-scheduler.xml
fair-scheduler.xml.template
mapred-queue-acls.xml
mapred-queue-acls.xml.template
mapred-site.xml
mapred-site.xml.template
taskcontroller.cfg
{noformat}
Files that should be in hdfs/conf
{noformat}
hdfs-site.xml
hdfs-site.xml.template
{noformat}
We could add configuration.xsl too (i.e. have it in all conf directories). Does this look right?
Also, the bin scripts are all in common - we should move these too.
hdfs/bin:
{noformat}
hdfs
hdfs-config.sh
start-balancer.sh
start-dfs.sh
stop-dfs.sh
{noformat}
mapreduce/bin:
{noformat}
mapred
mapred-config.sh
start-mapred.sh
stop-mapred.sh
{noformat}
> 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.
[jira] Commented: (MAPREDUCE-1033) Resolve location of
configuration files after project split
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12873815#action_12873815 ]
Tom White commented on MAPREDUCE-1033:
--------------------------------------
Sorry, third part patch is in HDFS-1181.
> 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
> Assignee: Tom White
> 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.
[jira] Commented: (MAPREDUCE-1033) Resolve location of scripts and
configuration files after project split
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877786#action_12877786 ]
Hudson commented on MAPREDUCE-1033:
-----------------------------------
Integrated in Hadoop-Common-trunk #363 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Common-trunk/363/])
HADOOP-6794. Move configuration and script files post split. Includes HDFS-1181, MAPREDUCE-1033.
> Resolve location of scripts and 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
> Assignee: Tom White
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: MAPREDUCE-1033.patch, MAPREDUCE-1033.patch, MAPREDUCE-1033.patch, 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.
[jira] Commented: (MAPREDUCE-1033) Resolve location of scripts and
configuration files after project split
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877624#action_12877624 ]
Hudson commented on MAPREDUCE-1033:
-----------------------------------
Integrated in Hadoop-Common-trunk-Commit #293 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Common-trunk-Commit/293/])
HADOOP-6794. Move configuration and script files post split. Includes HDFS-1181, MAPREDUCE-1033.
> Resolve location of scripts and 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
> Assignee: Tom White
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: MAPREDUCE-1033.patch, MAPREDUCE-1033.patch, MAPREDUCE-1033.patch, 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.
[jira] Commented: (MAPREDUCE-1033) Resolve location of
configuration files after project split
Posted by "Vinod K V (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874481#action_12874481 ]
Vinod K V commented on MAPREDUCE-1033:
--------------------------------------
+1 for the latest patch for mapreduce. I could successfully bring up a single node cluster using the patches for all the projects and HADOOP-6461.
> 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
> Assignee: Tom White
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: MAPREDUCE-1033.patch, MAPREDUCE-1033.patch, 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.
[jira] Updated: (MAPREDUCE-1033) Resolve location of scripts and
configuration files after project split
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated MAPREDUCE-1033:
---------------------------------
Status: Resolved (was: Patch Available)
Resolution: Fixed
I've just committed this.
> Resolve location of scripts and 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
> Assignee: Tom White
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: MAPREDUCE-1033.patch, MAPREDUCE-1033.patch, MAPREDUCE-1033.patch, 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.
[jira] Updated: (MAPREDUCE-1033) Resolve location of configuration
files after project split
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ 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
> 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
> Assignee: Tom White
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: MAPREDUCE-1033.patch, 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.
[jira] Updated: (MAPREDUCE-1033) Resolve location of configuration
files after project split
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated MAPREDUCE-1033:
---------------------------------
Status: Patch Available (was: Open)
Assignee: Tom White
> 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
> Assignee: Tom White
> 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.
[jira] Updated: (MAPREDUCE-1033) Resolve location of configuration
files after project split
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ 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
> 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
> Assignee: Tom White
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: MAPREDUCE-1033.patch, MAPREDUCE-1033.patch, 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.
[jira] Updated: (MAPREDUCE-1033) Resolve location of scripts and
configuration files after project split
Posted by "Vinod K V (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod K V updated MAPREDUCE-1033:
---------------------------------
Summary: Resolve location of scripts and configuration files after project split (was: Resolve location of configuration files after project split)
Hadoop Flags: [Reviewed]
> Resolve location of scripts and 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
> Assignee: Tom White
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: MAPREDUCE-1033.patch, MAPREDUCE-1033.patch, 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.