to me to fix flaws in functionality that officially doesn't
> exist. Those issues should be addressed in the scope of service versioning.
>
> Use-cases that you described are interesting and we should try to support
> them, but I don't think that we should implement functionality for all
&g
)
replace existing service with newer implementation, and there are a number
of potential problems you might encounter while doing so. But it doesn't
make much sense to me to fix flaws in functionality that officially doesn't
exist. Those issues should be addressed in the scope of service versioning
Ilya,
I think the proposed change definitely makes sense.
At the same time I think the scope of the ticket is too broad. It covers at
least two different aspects of service grid functionality:
- Very specific issue of service upgrade process which is caused by
current design flaw
Ilya,
Every Service Grid user will welcome this feature. Fully for it.
Mentioned in the ticket that it has to be documented before the ticket is
closed.
—
Denis
> On Aug 15, 2017, at 8:18 AM, Ilya Lantukh wrote:
>
> Igniters,
>
> Our current ServiceGrid
Igniters,
Our current ServiceGrid implementation lacks several important features,
one of which is ability to upgrade Service without downtime.
I've created ticket to add this feature:
https://issues.apache.org/jira/browse/IGNITE-6069.
To implement it, the following problems must be solved:
-
Ilya Lantukh created IGNITE-6069:
Summary: Service versioning
Key: IGNITE-6069
URL: https://issues.apache.org/jira/browse/IGNITE-6069
Project: Ignite
Issue Type: New Feature