You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by Steve Loughran <st...@cloudera.com.INVALID> on 2022/07/18 17:49:26 UTC
Fwd: [jira] [Created] (MAPREDUCE-7372) MapReduce set permission too late in copyJar method
could someone look at the PR for this,
https://github.com/apache/hadoop/pull/4026
I think it iis ok to go in without tests, but don't want to break things.
if someone else could also review, that would be great
---------- Forwarded message ---------
From: Zhang Dongsheng (Jira) <ji...@apache.org>
Date: Thu, 24 Feb 2022 at 03:53
Subject: [jira] [Created] (MAPREDUCE-7372) MapReduce set permission too
late in copyJar method
To: <ma...@hadoop.apache.org>
Zhang Dongsheng created MAPREDUCE-7372:
------------------------------------------
Summary: MapReduce set permission too late in copyJar method
Key: MAPREDUCE-7372
URL: https://issues.apache.org/jira/browse/MAPREDUCE-7372
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: mrv2
Affects Versions: 3.3.1
Reporter: Zhang Dongsheng
while execute copyJar in JobResourceUploader .the setPermission running
after setReplication,but setReplication need permission first.So if we set
restrict umask in project such as 0600, the mapreduce process will fail.
In patch file , I put setPermisson before setReplication.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org