[
https://issues.apache.org/jira/browse/PIG-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14165907#comment-14165907
]
Hitesh Shah commented on PIG-4199:
----------------------------------
[~rohini] The ACLs for the AM are considered to be "super-user" settings i.e.
anyone who is the AM ACLs list will have similar powers over all DAGs that run
within that session/AM. DAG ACLs were introduced for cases such as Hive ( when
using HiveServer2 ) where the AM is launched as user hive ( which is a super
user ) and queries submitted by different users are run as hive within the same
AM.
ACLs applied when looking at a DAG are a union of AM and DAG ACLs. Therefore if
DAG ACLs are not set, only the AM ACLs will take effect. If you are translating
from MR to Tez, you should only need to define the AM ACLs and not need to set
DAG ACLs until you end up with a use-case similar to that of Hive.
> Mapreduce ACLs should be translated to Tez ACLs
> -----------------------------------------------
>
> Key: PIG-4199
> URL: https://issues.apache.org/jira/browse/PIG-4199
> Project: Pig
> Issue Type: Sub-task
> Reporter: Rohini Palaniswamy
> Fix For: 0.14.0
>
>
> MR job view and modify ACLs need to be translated and set on Tez
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
