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/01/30 02:46:39 UTC

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

Hitesh Shah created TEZ-3082:
--------------------------------

             Summary: 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
            Assignee: Hitesh Shah


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)