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

Bibin A Chundatt edited comment on YARN-9039 at 11/29/18 11:16 AM:
-------------------------------------------------------------------

{quote}
But gets cumbersome when implementing application specific acls on the logs 
objects stored under that folder i.e granting access to other users to read the 
logs
{quote}
Logs CLI talks to Log Webservice instead of talking to storage directly and 
only yarn user has access to write/read from the log aggregation storage 
bucket. Can track this effort in a separate jira to fix the issue of YARN CLI 
imposing ACLs  --Yes ,If we have to support application ACL for logCLI.




was (Author: bibinchundatt):
{quote}
But gets cumbersome when implementing application specific acls on the logs 
objects stored under that folder i.e granting access to other users to read the 
logs
{quote}
Logs CLI talks to Log Webservice instead of talking to storage directly and 
only yarn user has access to write/read from the log aggregation storage 
bucket. Can track this effort in a separate jira to fix the issue of YARN CLI 
imposing ACLs  --If we have to support application ACL 



> App ACLs are not validated when serving logs from LogWebService
> ---------------------------------------------------------------
>
>                 Key: YARN-9039
>                 URL: https://issues.apache.org/jira/browse/YARN-9039
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: log-aggregation
>            Reporter: Suma Shivaprasad
>            Assignee: Suma Shivaprasad
>            Priority: Critical
>         Attachments: YARN-9039.1.patch, YARN-9039.2.patch
>
>
> App Acls are not being validated while serving logs through REST and UI2 via 
> Log Webservice



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to