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

Posted to issues@ignite.apache.org by "Nikolay Izhikov (Jira)" <ji...@apache.org> on 2021/01/07 10:50:00 UTC

[jira] [Commented] (IGNITE-13958) .Net: Avoid binary configuration on Compute invocation

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

Nikolay Izhikov commented on IGNITE-13958:
------------------------------------------

Hello, [~ptupitsyn]

Can you, please, take a look? - https://github.com/apache/ignite/pull/8634

> .Net: Avoid binary configuration on Compute 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
>
>
> 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)