It states that when this property is set to true "it allow the user to override the default user to queue mappings defined with the yarn.scheduler.capacity.queue-mappings property" , and indeed gives an example showing this (wrongly) expected behavior.
if yarn.scheduler.capacity.queue-mappings-override.enable is set to false then user's have more control on which queue they want to submit the application either by setting the queue name or from default mapping, in this case user specified queue name takes the precedence , but if yarn.scheduler.capacity.queue-mappings-override.enable set to true then admin's have more control and admin can override user's explicit settings.
In other words, what the property enables is the possibility for the administrator to use the property "yarn.scheduler.capacity.queue-mappings" to override what the user or application configuration states, and not the other way.
May please some of the most experienced contributors in this forum confirm this? and if that's the case, if it were possible that someone from the company could correct such and important error in the documentation?