[jira] [Assigned] (IGNITE-13607) .NET: Binary meta is not registered from QueryEntity on cache start when types are not present on server node

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

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

Pavel Tupitsyn reassigned IGNITE-13607:
---------------------------------------

    Assignee:     (was: Pavel Tupitsyn)

> .NET: Binary meta is not registered from QueryEntity on cache start when types are not present on server node
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-13607
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13607
>             Project: Ignite
>          Issue Type: Bug
>          Components: platforms, thin client
>            Reporter: Pavel Tupitsyn
>            Priority: Minor
>              Labels: .NET
>
> When {{QueryEntity}} is present in {{CacheConfiguration}}, {{GridQueryProcessor}} registers binary metadata for key and value types by looking up Java classes (IGNITE-5795) and .NET types (IGNITE-13160) and scanning attributes. In particular, Affinity Key is determined at this point and then cached for future use.
> However, when corresponding Java/.NET types are not present on the server node, affinity key can't be determined from annotations/attributes and is considered null.
> This can happens only with dynamic cache start in the following cases:
> * Thin clients - the most obvious case, classes are almost never present on server nodes
> * Thick clients
> * Server nodes with different classpath



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