myloginid opened a new pull request, #8656: URL: https://github.com/apache/hadoop/pull/8656
### Summary - Allow a single user-type placement rule to match multiple submitter usernames via a comma-separated `matches` value (e.g. `alice,bob,charlie`). - Wire the existing `OrMatcher` into JSON rule creation and legacy `u:` queue mappings. - Update Capacity Scheduler UI help text/validation and document the syntax. ### Motivation Administrators routing many discrete users to one queue today must create one 1:1 placement rule per user. Comma-separated usernames in one rule reduces config size and simplifies management. ### Changes - `MappingRuleMatchers.createUserMatcherFromMatches()` — parses comma-separated usernames; `*` still matches all users when the entire string is `*`. - `MappingRuleCreator` and `MappingRule.createLegacyRule()` — use the new factory for user rules. - JSON schema, CS UI, and `CapacityScheduler.md` updated. - Unit tests added in `TestMappingRuleCreator`, `TestMappingRuleMatchers`, and `TestMappingRule`. ### Test plan - [ ] `mvn test -pl hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager -Dtest=TestMappingRuleCreator,TestMappingRuleMatchers,TestMappingRule` - [ ] Verify JSON rule with `"matches": "alice,bob"` places apps for `alice`/`bob` only. - [ ] Verify legacy `u:alice,bob:queue1` mapping. - [ ] Verify `*` and single-user rules unchanged. Fixes: https://issues.apache.org/jira/browse/YARN-11972 Made with [Cursor](https://cursor.com) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
