You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Denis Mekhanikov (JIRA)" <ji...@apache.org> on 2017/09/05 13:14:00 UTC
[jira] [Commented] (IGNITE-5145) Support multiple service
deployment in API
[ https://issues.apache.org/jira/browse/IGNITE-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153619#comment-16153619 ]
Denis Mekhanikov commented on IGNITE-5145:
------------------------------------------
Tickets for propagation of changes to .NET integration are created: IGNITE-6271, IGNITE-6272.
> 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)