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 0BA90115C8 for ; Wed, 14 May 2014 09:16:22 +0000 (UTC) Received: (qmail 60863 invoked by uid 500); 14 May 2014 09:16:21 -0000 Delivered-To: apmail-hama-dev-archive@hama.apache.org Received: (qmail 60833 invoked by uid 500); 14 May 2014 09:16:21 -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 60824 invoked by uid 99); 14 May 2014 09:16:21 -0000 Received: from Unknown (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 May 2014 09:16:21 +0000 Date: Wed, 14 May 2014 09:16:21 +0000 (UTC) From: "Edward J. Yoon (JIRA)" To: dev@hama.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HAMA-901) Multi-job configuration interface for communicate among jobs. 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/HAMA-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward J. Yoon updated HAMA-901: -------------------------------- Affects Version/s: (was: 0.6.4) > Multi-job configuration interface for communicate among jobs. > ------------------------------------------------------------- > > Key: HAMA-901 > URL: https://issues.apache.org/jira/browse/HAMA-901 > Project: Hama > Issue Type: New Feature > Components: bsp core > Reporter: Edward J. Yoon > Assignee: Edward J. Yoon > > I'm thinking about adding multi-job configuration interface for communicate among multiple jobs. My main purpose is for launching two infinite real-time data processing BSP job and incremental learning BSP job. > I guess it's not difficult since we don't have message security yet. -- This message was sent by Atlassian JIRA (v6.2#6252)