You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Pavel Tupitsyn (JIRA)" <ji...@apache.org> on 2016/11/30 13:32:58 UTC

[jira] [Updated] (IGNITE-1427) .NET: Services - add support for non-deserializable AffinityKey

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

Pavel Tupitsyn updated IGNITE-1427:
-----------------------------------
    Summary: .NET: Services - add support for non-deserializable AffinityKey  (was: .Net: Services - add support for non-deserializable AffinityKey.)

> .NET: Services - add support for non-deserializable AffinityKey
> ---------------------------------------------------------------
>
>                 Key: IGNITE-1427
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1427
>             Project: Ignite
>          Issue Type: Task
>          Components: platforms
>    Affects Versions: 1.1.4
>            Reporter: Vladimir Ozerov
>              Labels: .net
>
> Currently if affinity key cannot be marshalled for some reason, it will break not only affected service descriptor, but all services API.
> We should catch marshalling exceptions and pass it to .Net in a wrapped form. These exception must be thrown only if user is trying to access problematic key explicitly.



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