Mailing-List: contact commits-help@ace.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ace.apache.org
Date: Tue, 22 Oct 2013 12:50:42 +0000 (UTC)
From: "J.W. Janssen (JIRA)" <jira@apache.org>
To: commits@ace.apache.org
Message-ID: <JIRA.12657741.1373902741739.103713.1382446242602@arcas>
In-Reply-To: <JIRA.12657741.1373902741739@arcas>
References: <JIRA.12657741.1373902741739@arcas>
Subject: [jira] [Commented] (ACE-374) Analysis: Batch job support
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

J.W. Janssen commented on ACE-374:
----------------------------------

analysis looks good to me, I've implemented a first set of gogo commands that implement this...

> Analysis: Batch job support
> ---------------------------
>
>                 Key: ACE-374
>                 URL: https://issues.apache.org/jira/browse/ACE-374
>             Project: ACE
>          Issue Type: Task
>          Components: Client Repository
>            Reporter: Marcel Offermans
>            Assignee: Marcel Offermans
>
> When scaling up, ACE might end up with lots of "customers" or tenants that, for example, share a single shop. In such cases, when you update the shop, you need to iterate over all customers and update their target and deployment repositories.
> What we need is a generic batch job support process that allows us to queue such jobs easily. This task is about writing an analysis on how best to implement this.


--
This message was sent by Atlassian JIRA
(v6.1#6144)