From commits-return-5433-archive-asf-public=cust-asf.ponee.io@ace.apache.org Sun Mar 18 08:18:05 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 460B1180645 for ; Sun, 18 Mar 2018 08:18:05 +0100 (CET) Received: (qmail 11118 invoked by uid 500); 18 Mar 2018 07:18:03 -0000 Mailing-List: contact commits-help@ace.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ace.apache.org Delivered-To: mailing list commits@ace.apache.org Received: (qmail 11103 invoked by uid 99); 18 Mar 2018 07:18:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 18 Mar 2018 07:18:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id B43071A03E9 for ; Sun, 18 Mar 2018 07:18:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -102.311 X-Spam-Level: X-Spam-Status: No, score=-102.311 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 3nwB9oXk-_Y8 for ; Sun, 18 Mar 2018 07:18:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 510885F175 for ; Sun, 18 Mar 2018 07:18:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 59468E0181 for ; Sun, 18 Mar 2018 07:18:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1006B2127D for ; Sun, 18 Mar 2018 07:18:00 +0000 (UTC) Date: Sun, 18 Mar 2018 07:18:00 +0000 (UTC) From: "jannie cass (JIRA)" To: commits@ace.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACE-374) Analysis: Batch job support 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/ACE-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16403889#comment-16403889 ] jannie cass commented on ACE-374: --------------------------------- very interesting work > 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 > Priority: Major > Fix For: 2.0.1 > > > 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 (v7.6.3#76005)