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

["Pavel Tupitsyn (Jira)" <ji...@apache.org>]

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

Pavel Tupitsyn commented on IGNITE-13958:
-----------------------------------------

[~nizhikov] 
1. Do we still need {{RegisterSameJavaType}} flag? Can we just register Java types at all times?
2. I have concerns about compatibility. In some scenarios we can cause {{DuplicateTypeIdException}} when registering Java type names like this - e.g. a custom name and/or id mapper is used on the Java side.

So my proposal is:
1. Remove {{Marhsaller.RegisterSameJavaType}}
2. Add a flag to {{BinaryConfiguration}} to enable this behavior for all use cases, {{false}} by default.

It would be great to discuss this on the dev list as well.

> .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
>          Components: platforms
>    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)