You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2008/11/19 19:50:44 UTC
[jira] Created: (HADOOP-4687) Split map/reduce into sub-project
Split map/reduce into sub-project
---------------------------------
Key: HADOOP-4687
URL: https://issues.apache.org/jira/browse/HADOOP-4687
Project: Hadoop Core
Issue Type: Task
Components: mapred
Reporter: Owen O'Malley
Assignee: Owen O'Malley
Fix For: 0.20.0
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4687) Split map/reduce into sub-project
Posted by "Giridharan Kesavan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711038#action_12711038 ]
Giridharan Kesavan commented on HADOOP-4687:
--------------------------------------------
With this split I'm also thinking about changing the folder structure to follow maven standards. Any comments?
tnx!
> Split map/reduce into sub-project
> ---------------------------------
>
> Key: HADOOP-4687
> URL: https://issues.apache.org/jira/browse/HADOOP-4687
> Project: Hadoop Core
> Issue Type: Task
> Components: mapred
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4687) Split map/reduce into sub-project
Posted by "Giridharan Kesavan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711047#action_12711047 ]
Giridharan Kesavan commented on HADOOP-4687:
--------------------------------------------
bq. What would those standards be?
java sources would go in here.
src/main/java
test sources would go in here
src/test/java
For details : http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
> Split map/reduce into sub-project
> ---------------------------------
>
> Key: HADOOP-4687
> URL: https://issues.apache.org/jira/browse/HADOOP-4687
> Project: Hadoop Core
> Issue Type: Task
> Components: mapred
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4687) Split map/reduce into sub-project
Posted by "Nigel Daley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711040#action_12711040 ]
Nigel Daley commented on HADOOP-4687:
-------------------------------------
What would those standards be?
> Split map/reduce into sub-project
> ---------------------------------
>
> Key: HADOOP-4687
> URL: https://issues.apache.org/jira/browse/HADOOP-4687
> Project: Hadoop Core
> Issue Type: Task
> Components: mapred
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4687) Split map/reduce into sub-project
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711088#action_12711088 ]
Tom White commented on HADOOP-4687:
-----------------------------------
As far as jar naming goes, how about
hadoop-{core,hdfs,mapred}-0.21.0-dev.jar
hadoop-{core,hdfs,mapred}-{ant,examples,test,tools}-0.21.0-dev.jar
Having the version number at the end seems to be the standard way to name things in the Ivy/Maven world.
> Split map/reduce into sub-project
> ---------------------------------
>
> Key: HADOOP-4687
> URL: https://issues.apache.org/jira/browse/HADOOP-4687
> Project: Hadoop Core
> Issue Type: Task
> Components: mapred
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4687) Split map/reduce into sub-project
Posted by "Nigel Daley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711171#action_12711171 ]
Nigel Daley commented on HADOOP-4687:
-------------------------------------
+1 on maven layout.
+1 on Tom's jar name suggestions.
Regarding jar names, we'll need to update bin scripts. Here are current references in the top-level bin scripts:
{code}
hadoop-config.sh:for f in $HADOOP_CORE_HOME/hadoop-*-core.jar; do
hadoop-config.sh:for f in $HADOOP_CORE_HOME/hadoop-*-tools.jar; do
hadoop-config.sh:for f in $HADOOP_CORE_HOME/build/hadoop-*-tools.jar; do
hadoop-config.sh: for f in $HADOOP_HDFS_HOME/hadoop-*-hdfs.jar; do
hdfs:for f in $HADOOP_HDFS_HOME/hadoop-*-hdfs.jar; do
mapred:for f in $HADOOP_MAPRED_HOME/hadoop-*-mapred.jar; do
rcc:for f in $HADOOP_HOME/hadoop-*-core.jar; do
{code}
Contrib bin scripts, Makefiles, etc also need to be checked and updated. Owen, this seems beyond what Giri should have to do for getting the build working. Should we file a separate Jira for that once the names are settled on.
> Split map/reduce into sub-project
> ---------------------------------
>
> Key: HADOOP-4687
> URL: https://issues.apache.org/jira/browse/HADOOP-4687
> Project: Hadoop Core
> Issue Type: Task
> Components: mapred
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4687) Split map/reduce into sub-project
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711041#action_12711041 ]
dhruba borthakur commented on HADOOP-4687:
------------------------------------------
I am assuming that HadoopQA will run all unit tests (both dfs and map-reduce) when a patch is submitted for the dfs sub-project (or for the map-reduce subproject).
> Split map/reduce into sub-project
> ---------------------------------
>
> Key: HADOOP-4687
> URL: https://issues.apache.org/jira/browse/HADOOP-4687
> Project: Hadoop Core
> Issue Type: Task
> Components: mapred
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-4687) Split map/reduce into sub-project
Posted by "Nigel Daley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710604#action_12710604 ]
Nigel Daley commented on HADOOP-4687:
-------------------------------------
Owen, thoughts on how we should rename these jar files in the mapred and hdfs projects?
hadoop-0.21.0-dev-ant.jar
hadoop-0.21.0-dev-core.jar
hadoop-0.21.0-dev-examples.jar
hadoop-0.21.0-dev-test.jar
hadoop-0.21.0-dev-tools.jar
> Split map/reduce into sub-project
> ---------------------------------
>
> Key: HADOOP-4687
> URL: https://issues.apache.org/jira/browse/HADOOP-4687
> Project: Hadoop Core
> Issue Type: Task
> Components: mapred
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.