Return-Path: X-Original-To: apmail-tez-issues-archive@minotaur.apache.org Delivered-To: apmail-tez-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 761E518A30 for ; Mon, 1 Feb 2016 22:40:40 +0000 (UTC) Received: (qmail 4008 invoked by uid 500); 1 Feb 2016 22:40:40 -0000 Delivered-To: apmail-tez-issues-archive@tez.apache.org Received: (qmail 3953 invoked by uid 500); 1 Feb 2016 22:40:40 -0000 Mailing-List: contact issues-help@tez.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tez.apache.org Delivered-To: mailing list issues@tez.apache.org Received: (qmail 3937 invoked by uid 99); 1 Feb 2016 22:40:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Feb 2016 22:40:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id E77B32C1F5C for ; Mon, 1 Feb 2016 22:40:39 +0000 (UTC) Date: Mon, 1 Feb 2016 22:40:39 +0000 (UTC) From: "Hitesh Shah (JIRA)" To: issues@tez.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (TEZ-3082) For non-framework history loggers, Tez should support a way to specify a custom policy manager MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/TEZ-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127175#comment-15127175 ] Hitesh Shah commented on TEZ-3082: ---------------------------------- [~sseth] [~zjffdu] [~jlowe] [~bikassaha] [~jeagles] any suggestions/comments on the approach or option solution options? > 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)