[YARN-11415] Refactor TestConfigurationFieldsBase and the connected test classes

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Not A Problem
• Labels: pull-request-available
• Assignee: Szilard Nemeth
• Reporter: Benjamin Teke
• Created: 11/Jan/23 10:07
• Updated: 06/Mar/23 11:56
• Resolved: 06/Mar/23 11:56

Description

YARN-11413 pointed out a strange way of how the configuration tests are executed. The first problem is that there is a Pattern, that matches only numbers, letters, dots, hyphens and underscores, but not %, which is used in string replacements (i.e yarn.nodemanager.aux-services.%s.classpath ), so essentially every property that's present in any configuration object and doesn't match this pattern is silently skipped, and documenting it will result in invalid test failures, ergo the test encourages introducing props and not documenting them. The pattern should be fixed in YARN-11413 for %s, but it's necessity could be checked.

Another issue with this is that it works in a semi-opposite way of what it's supposed to do. To ensure all of the configuration entries are documented it should iterate through all of the configuration fields and check if those have matching xyz-default.xml entries, but currently it just reports the entries that are present in the xyz-default.xml and missing in the matching configuration file. Since this test checks all the configuration objects this might need some other follow-ups to document the missing properties from other components if there are any.

Issue Links

• is related to: YARN-11450 Improvements for TestYarnConfigurationFields and TestConfigurationFieldsBase
• links to: GitHub Pull Request #5454