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 "Pete Wyckoff (JIRA)" <ji...@apache.org> on 2008/07/15 23:01:32 UTC
[jira] Created: (HADOOP-3763) Make fuse_dfs_wrapper.sh add the
fuse_dfs executable in the hadoop deployment directory to its path
Make fuse_dfs_wrapper.sh add the fuse_dfs executable in the hadoop deployment directory to its path
---------------------------------------------------------------------------------------------------
Key: HADOOP-3763
URL: https://issues.apache.org/jira/browse/HADOOP-3763
Project: Hadoop Core
Issue Type: Improvement
Components: contrib/fuse-dfs
Reporter: Pete Wyckoff
This will make it easier to do upgrades and debug configuration problems since we only have to copy the wrapper into a system directory - ie /bin and the wrapper changes rarely. (and it could be a symlink)
So I just propose adding
export PATH=$HADOOP_HOME/contrib/fuse_dfs:$PATH
to the wrapper script.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-3763) Move fuse_dfs_wrapper.sh and
fuse_dfs into the hadoop/contrib/fuse_dfs deploy directory and use
hadoop-env.sh to get env info
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617102#action_12617102 ]
Pete Wyckoff commented on HADOOP-3763:
--------------------------------------
I talked to Dhruba about this and asked about factoring out the CLASSPATH creation code in bin/hadoop into something like bin/hadoop-classpath.sh so that hadoop, fuse and potentially libhdfs applications could re-use it.
Now that I see doug is a watcher here, what do you think Doug? And if so, would we need to open a separate JIRA for that?
thanks, pete
> Move fuse_dfs_wrapper.sh and fuse_dfs into the hadoop/contrib/fuse_dfs deploy directory and use hadoop-env.sh to get env info
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-3763
> URL: https://issues.apache.org/jira/browse/HADOOP-3763
> Project: Hadoop Core
> Issue Type: Improvement
> Components: contrib/fuse-dfs
> Reporter: Pete Wyckoff
>
> include
> ../../bin/hadoop-config.sh and then hadoop-env to get JAVA_HOME, HADOOP_HOME and such.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-3763) Move fuse_dfs_wrapper.sh and fuse_dfs
into the hadoop/contrib/fuse_dfs deploy directory and use hadoop-env.sh to
get env info
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Wyckoff updated HADOOP-3763:
---------------------------------
Description:
include
../../bin/hadoop-config.sh and then hadoop-env to get JAVA_HOME, HADOOP_HOME and such.
was:
This will make it easier to do upgrades and debug configuration problems since we only have to copy the wrapper into a system directory - ie /bin and the wrapper changes rarely. (and it could be a symlink)
So I just propose adding
export PATH=$HADOOP_HOME/contrib/fuse_dfs:$PATH
to the wrapper script.
Summary: Move fuse_dfs_wrapper.sh and fuse_dfs into the hadoop/contrib/fuse_dfs deploy directory and use hadoop-env.sh to get env info (was: Make fuse_dfs_wrapper.sh add the fuse_dfs executable in the hadoop deployment directory to its path)
> Move fuse_dfs_wrapper.sh and fuse_dfs into the hadoop/contrib/fuse_dfs deploy directory and use hadoop-env.sh to get env info
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-3763
> URL: https://issues.apache.org/jira/browse/HADOOP-3763
> Project: Hadoop Core
> Issue Type: Improvement
> Components: contrib/fuse-dfs
> Reporter: Pete Wyckoff
>
> include
> ../../bin/hadoop-config.sh and then hadoop-env to get JAVA_HOME, HADOOP_HOME and such.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-3763) Move fuse_dfs_wrapper.sh and
fuse_dfs into the hadoop/contrib/fuse_dfs deploy directory and use
hadoop-env.sh to get env info
Posted by "Pete Wyckoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617107#action_12617107 ]
Pete Wyckoff commented on HADOOP-3763:
--------------------------------------
Another problem is that bin/hadoop-config.sh assumes you are calling it from the bin directory already.
> Move fuse_dfs_wrapper.sh and fuse_dfs into the hadoop/contrib/fuse_dfs deploy directory and use hadoop-env.sh to get env info
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-3763
> URL: https://issues.apache.org/jira/browse/HADOOP-3763
> Project: Hadoop Core
> Issue Type: Improvement
> Components: contrib/fuse-dfs
> Reporter: Pete Wyckoff
>
> include
> ../../bin/hadoop-config.sh and then hadoop-env to get JAVA_HOME, HADOOP_HOME and such.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-3763) Make fuse_dfs_wrapper.sh add the
fuse_dfs executable in the hadoop deployment directory to its path
Posted by "Craig Macdonald (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616942#action_12616942 ]
Craig Macdonald commented on HADOOP-3763:
-----------------------------------------
In similar lines, I would like to be able to directly call the script from autofs. If I point autofs to the wrapper script in the currently installed Hadoop version, can the wrapper script determine automatically the location of HADOOP_HOME? Perhaps it can even import conf/hadoop-env.sh?
> Make fuse_dfs_wrapper.sh add the fuse_dfs executable in the hadoop deployment directory to its path
> ---------------------------------------------------------------------------------------------------
>
> Key: HADOOP-3763
> URL: https://issues.apache.org/jira/browse/HADOOP-3763
> Project: Hadoop Core
> Issue Type: Improvement
> Components: contrib/fuse-dfs
> Reporter: Pete Wyckoff
>
> This will make it easier to do upgrades and debug configuration problems since we only have to copy the wrapper into a system directory - ie /bin and the wrapper changes rarely. (and it could be a symlink)
> So I just propose adding
> export PATH=$HADOOP_HOME/contrib/fuse_dfs:$PATH
> to the wrapper script.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-3763) Move fuse_dfs_wrapper.sh and
fuse_dfs into the hadoop/contrib/fuse_dfs deploy directory and use
hadoop-env.sh to get env info
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617496#action_12617496 ]
Doug Cutting commented on HADOOP-3763:
--------------------------------------
> factoring out the CLASSPATH creation code in bin/hadoop into something like bin/hadoop-classpath.sh
Sounds reasonable to me.
> Move fuse_dfs_wrapper.sh and fuse_dfs into the hadoop/contrib/fuse_dfs deploy directory and use hadoop-env.sh to get env info
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-3763
> URL: https://issues.apache.org/jira/browse/HADOOP-3763
> Project: Hadoop Core
> Issue Type: Improvement
> Components: contrib/fuse-dfs
> Reporter: Pete Wyckoff
>
> include
> ../../bin/hadoop-config.sh and then hadoop-env to get JAVA_HOME, HADOOP_HOME and such.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.