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

["Michael Griggs (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16182665#comment-16182665 ] 

Michael Griggs commented on IGNITE-6069:
----------------------------------------

>all service instances with the same name must have the same version

I think this ticket is a good opportunity to have multiple versions of a service available in the cluster at the same time.  By default requests would go to the latest version, but earlier versions could be requested by adding a parameter to the `serviceProxy()` method.  The service version could be better indicated using an attribute on the service implementation, rather than using serialVersionUuid.

> Service versioning
> ------------------
>
>                 Key: IGNITE-6069
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6069
>             Project: Ignite
>          Issue Type: New Feature
>          Components: general
>    Affects Versions: 2.1
>            Reporter: Ilya Lantukh
>            Assignee: Ilya Lantukh
>
> Make services upgradable -again-. 
> Main points:
> - compute binary type ID by (classname + version)
> - use serialVersionUuid as version ( ?)
> - all service instances with the same name must have the same version
> - make ServiceProxy aware of versions and upgrade process, pause requests while service is being upgraded
> - extend Service interface (UpgradableService?) - add ability to collect state of previous version before start.
> Once the feature is implemented, it has to be documented extensively. The ticket must not be closed until this happens.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)