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

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

    [ https://issues.apache.org/jira/browse/TEZ-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124685#comment-15124685 ] 

TezQA commented on TEZ-3082:
----------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment
  http://issues.apache.org/jira/secure/attachment/12785310/TEZ-3082.1.wip.config-based.patch
  against master revision 870972d.

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version 3.0.1) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/1441//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1441//console

This message is automatically generated.

> 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
>         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)