[
https://issues.apache.org/jira/browse/IGNITE-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157569#comment-16157569
]
Dmitriy Setrakyan edited comment on IGNITE-5145 at 9/7/17 8:16 PM:
-------------------------------------------------------------------
As was discussed on the dev@ list, the API should only have one method:
{{deployAll(Collection<ServiceConfiguration>) throws
ServiceDeploymentException}}.
The exception thrown should have a list of services that failed deployment, and
possibly the error messages.
was (Author: dsetrakyan):
As was discussed on the dev@ list, the API should only have one method:
{{deployAll(Collection<ServiceConfiguration>) throws
ServiceDeploymentException}}. The exception thrown should have a list of
services that failed deployment, and possibly the error messages.
> 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<ServiceConfiguration>, boolean)}} and
> {{deployAllAsync(Collection<ServiceConfiguration>, 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)
