[ 
https://issues.apache.org/jira/browse/YARN-10135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17043858#comment-17043858
 ] 

Szilard Nemeth commented on YARN-10135:
---------------------------------------

Hi [~pbacsko],
Patch looks good to me, committed to trunk!
Resolving jira.

> FS-CS converter tool: issue warning on dynamic auto-create mapping rules
> ------------------------------------------------------------------------
>
>                 Key: YARN-10135
>                 URL: https://issues.apache.org/jira/browse/YARN-10135
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Peter Bacsko
>            Assignee: Peter Bacsko
>            Priority: Major
>              Labels: fs2cs
>         Attachments: YARN-10135-001.patch, YARN-10135-002.patch
>
>
> The converter tool should issue a warning whenever the conversion results in 
> mapping rules similar to these:
> {{u:%user:[managedParentQueueName].[queueName]}}
> {{u:%user:[managedParentQueueName].%user}}
> {{u:%user:[managedParentQueueName].%primary_group}}
> {{u:%user:[managedParentQueueName].%secondary_group}}
> {{u:%user:%primary_group.%user}}
> {{u:%user:%secondary_group.%user}}
> {{u:%user:[managedParentQueuePath].%user}}
>  
> The reason is that right now it's fully clear how we'll handle a case like 
> "u:%user:%primary_group.%user", where "%primary_group.%user" might result in 
> something like "users.john". 
> In case of "u:%user:[managedParentQueuePath].%user" , the 
> [managedParentQueuePath] is a result of a full path from Fair Scheduler. 
> Therefore it's not going to be a leaf queue. 
> The user might be required to do some fine tuning and adjust the property 
> "auto-create-child-queues". We should display a warning about these 
> additional steps.
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to