[
https://issues.apache.org/jira/browse/TEZ-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15443069#comment-15443069
]
Harish Jaiprakash commented on TEZ-3404:
----------------------------------------
Thanks [~hitesh].
bq. Definitely not ok to change behavior. The unit test definitely should not
change to account for a behavior modification. Please revert. No dag acls
implies only the dag owner should be the only one to be able to view the dag.
Not setting a domain means all data is visible to everyone.
The change of behaviour was only creating another domain with the same acls
instead of using session doamin, I've changed it to make the behaviour same as
the previous implementation.
bq. Waiting for all the services to start might mean that the launched event
never goes through if one of the services fails to start. It would be good to
see if we can address this dependency in a clean way.
I have not fixed this one, currently it enqueues it into the queue and when the
service actually starts it make the ATS calls.
bq. This was being done earlier probably as a result of using config to
communicate with the pluggable policy managers. Might be a good idea to fix
this correctly.
Done, removed the serialization code into conf completely.
> Remove blocking call for ATS domain creation from client side to AM
> -------------------------------------------------------------------
>
> Key: TEZ-3404
> URL: https://issues.apache.org/jira/browse/TEZ-3404
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Harish Jaiprakash
> Assignee: Harish Jaiprakash
> Attachments: TEZ-3404-WIP-01.patch, TEZ-3404-WIP-02.patch,
> TEZ-3404-WIP-03.patch, TEZ-3404-WIP-04.patch, TEZ-3404-WIP-05.patch,
> TEZ-3404-WIP-06.patch
>
>
> Today, there is a blocking call for creating the domain on the client side
> which blocks hive query throughput. We need to move this to the AM and still
> retain the same security guarantees.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
