Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 86D9E200CFA for ; Tue, 5 Sep 2017 17:34:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 85A80161421; Tue, 5 Sep 2017 15:34:10 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D7345160BE4 for ; Tue, 5 Sep 2017 17:34:09 +0200 (CEST) Received: (qmail 96708 invoked by uid 500); 5 Sep 2017 15:34:08 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 96532 invoked by uid 99); 5 Sep 2017 15:34:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Sep 2017 15:34:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 27AA7CA285 for ; Tue, 5 Sep 2017 15:34:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.201 X-Spam-Level: X-Spam-Status: No, score=-99.201 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id xCaw1GP031jy for ; Tue, 5 Sep 2017 15:34:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 9321A6126E for ; Tue, 5 Sep 2017 15:34: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 13377E0EF9 for ; Tue, 5 Sep 2017 15:34:01 +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 6397A24158 for ; Tue, 5 Sep 2017 15:34:00 +0000 (UTC) Date: Tue, 5 Sep 2017 15:34:00 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (IGNITE-5145) Support multiple service deployment in API MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 05 Sep 2017 15:34:10 -0000 [ https://issues.apache.org/jira/browse/IGNITE-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153846#comment-16153846 ] ASF GitHub Bot commented on IGNITE-5145: ---------------------------------------- Github user dmekhanikov closed the pull request at: https://github.com/apache/ignite/pull/2450 > Support multiple service deployment in API > ------------------------------------------ > > Key: IGNITE-5145 > URL: https://issues.apache.org/jira/browse/IGNITE-5145 > Project: Ignite > Issue Type: Improvement > Affects Versions: 2.0 > Reporter: Dmitry Karachentsev > Assignee: Denis Mekhanikov > Fix For: 2.3 > > > IgniteServices should support possibility of deploying batch of services at once to speed up deployment. > It implies the following API changes: > * introduce {{ServiceDeploymentException}}, indicating that some problems were encountered during deployment process and containing a list of failed services; > * add {{deployAll(Collection, boolean)}} and {{deployAllAsync(Collection, boolean)}} methods to {{IgniteServices}} interface. Boolean flag shows whether we should follow "all-or-none" failing policy, or allow partial deployments. > Also all async methods in {{IgniteServices}} should not throw any exceptions, but return a future, whose {{get}} method should throw an exception if any errors occur during deployment. -- This message was sent by Atlassian JIRA (v6.4.14#64029)