[YARN-10620] fs2cs: parentQueue for certain placement rules are not set during conversion

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.0
• Fix Version/s: 3.4.0
• Component/s: capacity scheduler
• Labels: fs2cs
• Target Version/s: 3.4.0
• Hadoop Flags: Reviewed
• Assignee: Peter Bacsko
• Reporter: Peter Bacsko
• Created: 09/Feb/21 16:21
• Updated: 12/Feb/24 01:17
• Resolved: 10/Feb/21 10:16

Description

There are some placement rules in FS which are currently not handled properly by fs2cs:

<queuePlacementPolicy>
        <rule name="user" create="true"/>
        <rule name="primaryGroup" create="true"/>
    </queuePlacementPolicy>

The first rule means that if the user queue doesn't exist, it should be created as root.<user>.
The second means the same thing, except refers to the primary group instead of the submitting user: root.<primaryGroup>.

The problem is that in order for the create="true" setting to take effect, we must set the parent queue in the generated JSON:

Current:

{
  "rules" : [ {
    "type" : "user",
    "matches" : "*",
    "policy" : "user",
    "fallbackResult" : "skip",
    "create" : true
  }, {
    "type" : "user",
    "matches" : "*",
    "policy" : "primaryGroup",
    "fallbackResult" : "skip",
    "create" : true
  } ]
}

Expected:

{
  "rules" : [ {
    "type" : "user",
    "matches" : "*",
    "policy" : "user",
    "fallbackResult" : "skip",
    "parentQueue": "root",
    "create" : true
  }, {
    "type" : "user",
    "matches" : "*",
    "policy" : "primaryGroup",
    "fallbackResult" : "skip",
    "parentQueue": "root",
    "create" : true
  } ]

This is missing right now and it need to be fixed.