You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Hitesh Shah (JIRA)" <ji...@apache.org> on 2016/04/04 21:36:25 UTC
[jira] [Updated] (TEZ-3177) Non-DAG events should use the session
domain or no domain if the data does not need protection
[ https://issues.apache.org/jira/browse/TEZ-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hitesh Shah updated TEZ-3177:
-----------------------------
Attachment: TEZ-3177.2.patch
If acls enabled, session domain should always be set even if dag domain is not.
Regardless - agree with your review comment. Reworked code to make it more clear to understand the different paths. Please take a look.
> Non-DAG events should use the session domain or no domain if the data does not need protection
> -----------------------------------------------------------------------------------------------
>
> Key: TEZ-3177
> URL: https://issues.apache.org/jira/browse/TEZ-3177
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Hitesh Shah
> Assignee: Hitesh Shah
> Attachments: TEZ-3177.1.patch, TEZ-3177.2.patch
>
>
> There have been issues noticed where when using dag specific domains, container events get generated under different dags causing issues as they are updated using different domains.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)