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 2020/10/21 17:13:00 UTC

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

Pavel Tupitsyn created IGNITE-13607:
---------------------------------------

             Summary: .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
            Assignee: Pavel Tupitsyn
             Fix For: 2.10


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)