[
https://issues.apache.org/jira/browse/HIVE-15935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888958#comment-15888958
]
Siddharth Seth commented on HIVE-15935:
---------------------------------------
+1 for the latest patch.
[~daijy] - I believe this is using the fact that the executor is at max a
single thread, to make sure the domain gets registered first. Could you please
add a comment next to the executor before committing.
Need a couple of follow up jiras around ATS domains 1) Share the domainId
across Hive, and with Tez, 2) Handling domainId failures - maybe re-create
sessions? I'll create these
> ACL is not set in ATS data
> --------------------------
>
> Key: HIVE-15935
> URL: https://issues.apache.org/jira/browse/HIVE-15935
> Project: Hive
> Issue Type: Bug
> Reporter: Daniel Dai
> Assignee: Daniel Dai
> Attachments: HIVE-15935.1.patch, HIVE-15935.2.patch,
> HIVE-15935.3.patch, HIVE-15935.4.patch, HIVE-15935.5.patch
>
>
> When publishing ATS info, Hive does not set ACL, that make Hive ATS entries
> visible to all users. On the other hand, Tez ATS entires is using Tez DAG ACL
> which limit both view/modify ACL to end user only. We shall make them
> consistent. In the Jira, I am going to limit ACL to end user for both Tez ATS
> and Hive ATS, also provide config "hive.view.acls" and "hive.modify.acls" if
> user need to overridden.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
