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 "stack@archive.org (JIRA)" <ji...@apache.org> on 2006/04/19 19:59:44 UTC
[jira] Created: (HADOOP-149) TaskTracker#unJar trashes file modes
TaskTracker#unJar trashes file modes
------------------------------------
Key: HADOOP-149
URL: http://issues.apache.org/jira/browse/HADOOP-149
Project: Hadoop
Type: Bug
Versions: 0.2
Environment: linux
Reporter: stack@archive.org
Priority: Minor
Last Changed Rev: 395069
The unJar'ing of the job 'jar', trashes any file modes I've lovingly set at zip time. This is a bit of a pain when my job wants to run external scripts and I want to bundle the scripts up in the jar itself for distribution out to slaves.
I ain't sure how to address the issue though. Nought about unix file modes in JarEntry nor ZipEntry. I tried the ant 1.6.5 task unjar and unzip tasks thinking they'd respect file modes but they do same as TaskTracker#unJar (Commons zip makes mention of unix file modes but I haven't tried it). Perhaps support for jobs as tar(.gz) bundles? (But again, couldn't use ant to untar. It does same as unzip/unjar trashing file permissions).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (HADOOP-149) TaskTracker#unJar trashes file modes
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-149?page=all ]
Doug Cutting closed HADOOP-149:
-------------------------------
Resolution: Won't Fix
> TaskTracker#unJar trashes file modes
> ------------------------------------
>
> Key: HADOOP-149
> URL: http://issues.apache.org/jira/browse/HADOOP-149
> Project: Hadoop
> Type: Bug
> Versions: 0.2
> Environment: linux
> Reporter: stack@archive.org
> Priority: Minor
>
> Last Changed Rev: 395069
> The unJar'ing of the job 'jar', trashes any file modes I've lovingly set at zip time. This is a bit of a pain when my job wants to run external scripts and I want to bundle the scripts up in the jar itself for distribution out to slaves.
> I ain't sure how to address the issue though. Nought about unix file modes in JarEntry nor ZipEntry. I tried the ant 1.6.5 task unjar and unzip tasks thinking they'd respect file modes but they do same as TaskTracker#unJar (Commons zip makes mention of unix file modes but I haven't tried it). Perhaps support for jobs as tar(.gz) bundles? (But again, couldn't use ant to untar. It does same as unzip/unjar trashing file permissions).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (HADOOP-149) TaskTracker#unJar trashes file modes
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-149?page=comments#action_12375173 ]
Doug Cutting commented on HADOOP-149:
-------------------------------------
Yes, this is a pain. I think the root of the problem is that file modes are not cross-platform, so Java doesn't have an API to access them.
As a work-around, can you, instead of directly invoking your scripts, invoke '/bin/bash myScript.sh'? That way you don't require things to be executable.
> TaskTracker#unJar trashes file modes
> ------------------------------------
>
> Key: HADOOP-149
> URL: http://issues.apache.org/jira/browse/HADOOP-149
> Project: Hadoop
> Type: Bug
> Versions: 0.2
> Environment: linux
> Reporter: stack@archive.org
> Priority: Minor
>
> Last Changed Rev: 395069
> The unJar'ing of the job 'jar', trashes any file modes I've lovingly set at zip time. This is a bit of a pain when my job wants to run external scripts and I want to bundle the scripts up in the jar itself for distribution out to slaves.
> I ain't sure how to address the issue though. Nought about unix file modes in JarEntry nor ZipEntry. I tried the ant 1.6.5 task unjar and unzip tasks thinking they'd respect file modes but they do same as TaskTracker#unJar (Commons zip makes mention of unix file modes but I haven't tried it). Perhaps support for jobs as tar(.gz) bundles? (But again, couldn't use ant to untar. It does same as unzip/unjar trashing file permissions).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (HADOOP-149) TaskTracker#unJar trashes file modes
Posted by "stack@archive.org (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-149?page=comments#action_12375187 ]
stack@archive.org commented on HADOOP-149:
------------------------------------------
That'll do. Thanks.
I'd suggest that you can close this issue. The suggested workaround -- a /bin/bash or /usr/bin/env prefix -- will likely work for most.
> TaskTracker#unJar trashes file modes
> ------------------------------------
>
> Key: HADOOP-149
> URL: http://issues.apache.org/jira/browse/HADOOP-149
> Project: Hadoop
> Type: Bug
> Versions: 0.2
> Environment: linux
> Reporter: stack@archive.org
> Priority: Minor
>
> Last Changed Rev: 395069
> The unJar'ing of the job 'jar', trashes any file modes I've lovingly set at zip time. This is a bit of a pain when my job wants to run external scripts and I want to bundle the scripts up in the jar itself for distribution out to slaves.
> I ain't sure how to address the issue though. Nought about unix file modes in JarEntry nor ZipEntry. I tried the ant 1.6.5 task unjar and unzip tasks thinking they'd respect file modes but they do same as TaskTracker#unJar (Commons zip makes mention of unix file modes but I haven't tried it). Perhaps support for jobs as tar(.gz) bundles? (But again, couldn't use ant to untar. It does same as unzip/unjar trashing file permissions).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira