Return-Path: X-Original-To: apmail-hama-dev-archive@www.apache.org Delivered-To: apmail-hama-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 82527DD7D for ; Mon, 12 Nov 2012 11:35:17 +0000 (UTC) Received: (qmail 90927 invoked by uid 500); 12 Nov 2012 11:35:17 -0000 Delivered-To: apmail-hama-dev-archive@hama.apache.org Received: (qmail 90780 invoked by uid 500); 12 Nov 2012 11:35:16 -0000 Mailing-List: contact dev-help@hama.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hama.apache.org Delivered-To: mailing list dev@hama.apache.org Received: (qmail 90758 invoked by uid 99); 12 Nov 2012 11:35:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Nov 2012 11:35:16 +0000 Date: Mon, 12 Nov 2012 11:35:16 +0000 (UTC) From: "Thomas Jungblut (JIRA)" To: dev@hama.apache.org Message-ID: <428209194.100082.1352720116225.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (HAMA-672) Overload Jobsubmission in core module MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Thomas Jungblut created HAMA-672: ------------------------------------ Summary: Overload Jobsubmission in core module Key: HAMA-672 URL: https://issues.apache.org/jira/browse/HAMA-672 Project: Hama Issue Type: Sub-task Reporter: Thomas Jungblut introduce new configuration key "bsp.framework.name" which maps to the values: "local,classic,yarn" It will change core's BSPJob, so the client can be overloaded via a static mapping of value->classname. (e.G. local->LocalBSPRunner, classic->BSPMaster and a new implementation of the JobSubmissionProtocol for YARN). So we don't have to introduce a cyclic dependency from core->yarn and yarn->core, because core->yarn is then decoupled by a jobmission classname mapping. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira