[MAPREDUCE-5483] revert MAPREDUCE-5357

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.0-beta
• Fix Version/s: 2.1.1-beta
• Component/s: distcp
• Hadoop Flags: Reviewed
• Assignee: Robert Kanter
• Reporter: Alejandro Abdelnur
• Created: 27/Aug/13 18:22
• Updated: 24/Sep/13 23:33
• Resolved: 29/Aug/13 19:28

Description

MAPREDUCE-5357 does a fileystem chown() operation. chown() is not valid unless you are superuser. if you a chown() to yourself is a NOP, that is why has not been detected in Hadoop testcases where user is running as itself. However, in distcp testcases run by Oozie which use test users/groups from UGI for minicluster it is failing because of this chown() either because the test user does not exist of because the current use does not have privileges to do a chown().

We should revert MAPREDUCE-5357. Windows should handle this with some conditional logic used only when running in Windows.

Opening a new JIRA and not reverting directly because MAPREDUCE-5357 went in 2.1.0-beta.

Issue Links

• is broken by: MAPREDUCE-5357 Job staging directory owner checking could fail on Windows