ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Valentin Kulichenko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-3056) Service implementation class is required even if it's not expected to be deployed on current node
Date Tue, 26 Apr 2016 21:37:12 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Valentin Kulichenko updated IGNITE-3056:
----------------------------------------
    Description: Currently the service instance is deserialized as part of {{GridServiceDeployment}}
and {{GridServiceAssignment}} classes. Need to check if it's possible to deserialize only
node filter first, and then deserialize the service itself only if needed. This will allow
to use cluster groups with services and deploy the classes accordingly.

> Service implementation class is required even if it's not expected to be deployed on
current node
> -------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-3056
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3056
>             Project: Ignite
>          Issue Type: Bug
>          Components: managed services
>    Affects Versions: 1.5.0.final
>            Reporter: Valentin Kulichenko
>            Assignee: Valentin Kulichenko
>              Labels: community, customer, important
>             Fix For: 1.6
>
>
> Currently the service instance is deserialized as part of {{GridServiceDeployment}} and
{{GridServiceAssignment}} classes. Need to check if it's possible to deserialize only node
filter first, and then deserialize the service itself only if needed. This will allow to use
cluster groups with services and deploy the classes accordingly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message