[
https://issues.apache.org/jira/browse/TEZ-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15466751#comment-15466751
]
Harish Jaiprakash commented on TEZ-3404:
----------------------------------------
bq. The same tez client if used to submit multiple dags in non-session mode
will pollute the am configs.
Fixed.
bq. does this need to change?
Fixed, sorry did not see that.
bq. from a code clarity perspective, shouldn't historyACLPolicyManager == null
be in its own if clause and return null?
Done.
bq. code would be cleaner if the non-session mode was handled first in the if
clause. Also, docs need improvement to explain the non session code path. Docs
also reference sessionDomainId in createDAGDomain().
Done.
bq. In any case, we should probably clarify the behavior change.
Added documentation for HistoryACLPolicyManager, but I think we should just
remove that interface. There is no reason it has to be there anymore
> 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-09.patch, TEZ-3404-10.patch,
> 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,
> TEZ-3404-WIP-07.patch, TEZ-3404-WIP-08.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)
