[HADOOP-15866] Renamed HADOOP_SECURITY_GROUP_SHELL_COMMAND_TIMEOUT keys break compatibility

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.10.0, 3.2.0, 3.1.1, 2.9.2, 3.0.4, 3.3.0
• Fix Version/s: 2.10.0, 3.2.0, 2.9.2, 3.0.4, 3.3.0, 3.1.2
• Assignee: Wei-Chiu Chuang
• Reporter: Wei-Chiu Chuang
• Created: 19/Oct/18 22:33
• Updated: 07/Nov/18 01:34
• Resolved: 22/Oct/18 10:11

Description

Our internal tool found HADOOP-15523 breaks public API compatibility:

class CommonConfigurationKeysPublic

	Change	Effect
1	Field HADOOP_SECURITY_GROUP_SHELL_COMMAND_TIMEOUT_SECS has been renamed to HADOOP_SECURITY_GROUP_SHELL_COMMAND_TIMEOUT_KEY.	Recompilation of a client program may be terminated with the message: cannot find variable HADOOP_SECURITY_GROUP_SHELL_COMMAND_TIMEOUT_SECS in CommonConfigurationKeysPublic.
2	Field HADOOP_SECURITY_GROUP_SHELL_COMMAND_TIMEOUT_SECS_DEFAULT has been renamed to HADOOP_SECURITY_GROUP_SHELL_COMMAND_TIMEOUT_DEFAULT.	Recompilation of a client program may be terminated with the message: cannot find variable HADOOP_SECURITY_GROUP_SHELL_COMMAND_TIMEOUT_SECS_DEFAULT in CommonConfigurationKeysPublic.

HADOOP_SECURITY_GROUP_SHELL_COMMAND_TIMEOUT_SECS_DEFAULT is used to instantiate a variable in ShellBasedGroupsMapping objects, and since almost all applications requires groups mapping, this can cause runtime error if application loads multiple versions of Hadoop library.

IMO this is a blocker for 3.2.0

Issue Links

• is caused by: HADOOP-15523 Shell command timeout given is in seconds whereas it is taken as millisec while scheduling