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

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: platforms, thin client
• Labels: .NET
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Unassigned
• Reporter: Pavel Tupitsyn
• Created: 21/Oct/20 17:12
• Updated: 22/Jun/21 14:10

Description

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

Issue Links

• is caused by: IGNITE-13160 .NET: wrong affinity key registration with AffinityKeyMapped attribute