You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@ace.apache.org by "Marcel Offermans (JIRA)" <ji...@apache.org> on 2014/04/17 10:57:01 UTC

[jira] [Closed] (ACE-374) Analysis: Batch job support

     [ https://issues.apache.org/jira/browse/ACE-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Offermans closed ACE-374.
--------------------------------

    Resolution: Fixed

Closed all issues I just reopened and targeted for 'next' release.

> 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
>             Fix For: next
>
>
> 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.2#6252)