Re: Service versioning

2017-10-03 Thread Denis Mekhanikov
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

Re: Service versioning

2017-08-18 Thread Ilya Lantukh
) 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

Re: Service versioning

2017-08-16 Thread Sergey Chugunov
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

Re: Service versioning

2017-08-15 Thread Denis Magda
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

Service versioning

2017-08-15 Thread Ilya Lantukh
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: -

[jira] [Created] (IGNITE-6069) Service versioning

2017-08-15 Thread Ilya Lantukh (JIRA)
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