You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "jay vyas (JIRA)" <ji...@apache.org> on 2014/04/16 21:20:15 UTC

[jira] [Updated] (YARN-1952) getRunAsUser should be overridable (outside of package)

     [ https://issues.apache.org/jira/browse/YARN-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jay vyas updated YARN-1952:
---------------------------

    Summary: getRunAsUser should be overridable (outside of package)   (was: getRunAsUser should be overridable )

> getRunAsUser should be overridable (outside of package) 
> --------------------------------------------------------
>
>                 Key: YARN-1952
>                 URL: https://issues.apache.org/jira/browse/YARN-1952
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager
>            Reporter: jay vyas
>
> The getRunAsUser implementation is package private, but there is no comment stating why. 
> * I suggest we open it up so that we can override it without having to write code in a special hadoop namespace.
> Alternatively: 
> * Lets provide a clear comment about why its package private, if there is a good reason. 
> Here is my justification for making the method public. 
> There are certain implementations where we want more nuanced LCE behaviour.  
> In one case, we might want to allow users to override the behaviour of YARN-1235 (i.e. in highly secured clusters) 
> {noformat}
>  getRunAsUser(String u){ return u ; } 
> {noformat} 
> Or maybe I'd want to route different users to different super implementations: 
> {noformat}
> mary,tom,sally -> execute using analytics1
> joe,bob,kim -> execute using analytics2
> jim,cara -> nobody 
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2#6252)