[jira] [Updated] (TEZ-3082) For non-framework history loggers, Tez should support a way to specify a custom policy manager

["Hitesh Shah (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TEZ-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hitesh Shah updated TEZ-3082:
-----------------------------
    Assignee:     (was: Hitesh Shah)

> For non-framework history loggers, Tez should support a way to specify a custom policy manager
> ----------------------------------------------------------------------------------------------
>
>                 Key: TEZ-3082
>                 URL: https://issues.apache.org/jira/browse/TEZ-3082
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Hitesh Shah
>         Attachments: TEZ-3082.1.wip.config-based.patch
>
>
> For framework supported policy managers, the rules of mapping history service to policy manager can be baked into code. For 3rd party impls, a simple config approach may suffice. 
> Ideally querying the HistoryLoggingService class should also work but that requires ripping out AppContext ( AppContext is in tez-dag, the logging  interfaces need to be in tez-api ). Another approach would be via serviceloaders/pluggable factories that given a conf/history logging class construct and return back a policy manager. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)