hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sharad Agarwal (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-4868) Split the hadoop script into 3 parts
Date Wed, 04 Feb 2009 13:25:59 GMT

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

Sharad Agarwal updated HADOOP-4868:

    Attachment: 4868_v4.patch

ok, I have kept the scripts in bin/ itself. This keeps things simple and full backward compatibility
is maintained. The scripts have been refactored in such a fashion that when the split happens,
the scripts can go in their respective sub projects; and very few environment variable flips
are required (only in the *-config.sh files). 
Tested by emulating the case where the bin/* scripts are run as if the project split has happened.
Also tested in local and distributed mode.

bq. Should we name this "core-config.sh" to be consistent?
I have kept the config name as same "hadoop-config.sh". I think we can retain the same name
as the core script is also named "hadoop" 

> Split the hadoop script into 3 parts
> ------------------------------------
>                 Key: HADOOP-4868
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4868
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: scripts
>            Reporter: Sharad Agarwal
>            Assignee: Sharad Agarwal
>         Attachments: 4868_v1.patch, 4868_v2.patch, 4868_v3.patch, 4868_v4.patch
> We need to split the bin/hadoop into 3 parts for core, mapred and hdfs. This will enable
us to distribute the individual scripts with each component.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message