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 2021/01/07 16:49:00 UTC

[jira] [Updated] (IGNITE-13958) .NET: Avoid binary configuration on Compute and Cache API invocation

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

Pavel Tupitsyn updated IGNITE-13958:
------------------------------------
    Summary: .NET: Avoid binary configuration on Compute and Cache API invocation  (was: .Net: Avoid binary configuration on Compute and Cache API invocation)

> .NET: Avoid binary configuration on Compute and Cache API invocation
> --------------------------------------------------------------------
>
>                 Key: IGNITE-13958
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13958
>             Project: Ignite
>          Issue Type: Improvement
>    Affects Versions: 2.9.1
>            Reporter: Nikolay Izhikov
>            Assignee: Nikolay Izhikov
>            Priority: Major
>              Labels: .NET
>             Fix For: 2.10
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently, it's required to explicitly register any custom user type as a binary type to be able to invoke some compute API method with this type as a parameter or return value.
> We should use the same technique as in IGNITE-10075 to avoid explicit binary type registration.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)