[
https://issues.apache.org/jira/browse/TEZ-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14091373#comment-14091373
]
Hitesh Shah commented on TEZ-671:
---------------------------------
bq. getACLManager should make use of getDAG - instead of replicating it
- being addressed.
bq, Oleg had a comment about getting the ugi being repeated everywhere
- already addressed.
bq. Are any changes required on the creation of the
ApplicationSubmissionContext to set the AM ACLs for YARN
- being addressed.
bq. How to DAGs supply ACLs. Do we need a method on the DAG API for this. In,
which case, the DAG specific config parameters are likely not required.
- I was under the assumption that we had support for a separate additional
dag conf as a pass through for dag specific params. This seems no longer the
case so I guess a new API is needed.
bq. Anything needed in terms of ATS, or will that be a separate patch.
- follow-up once timeline acls supports comes into hadoop. Post 2.6 i guess.
bq. Ideally, when using the SimpleHistoryLoggingService - we could use HDFS
ACLs to give access specific AM logs, but this would be a follow up.
- Will file a follow-up for this too.
bq. In terms of Group, AclManager etc
- Groups was the only one I would have liked to reuse. It still has features
being added and is marked private so I ended up creating a copy.
- As for AclManager and all the other common functionality, given our need
for 2 level checks, I think a separate impl might be better for us.
> Support View/Modify ACLs for DAGs
> ---------------------------------
>
> Key: TEZ-671
> URL: https://issues.apache.org/jira/browse/TEZ-671
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Siddharth Seth
> Assignee: Hitesh Shah
> Attachments: TEZ-671.2.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
