[
https://issues.apache.org/jira/browse/IGNITE-14293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-14293:
------------------------------------
Ignite Flags: (was: Release Notes Required)
> .NET: AffinityKey does not work
> -------------------------------
>
> Key: IGNITE-14293
> URL: https://issues.apache.org/jira/browse/IGNITE-14293
> Project: Ignite
> Issue Type: Bug
> Components: platforms
> Affects Versions: 2.10
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Blocker
> Labels: .NET
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{AffinityKey}} does not work as expected - {{Affinity}} property is not used
> for affinity calculation.
> This is caused by IGNITE-13160: {{AffinityKey}} system type is overwritten by
> {{UnmanagedCallbacks.BinaryTypeGet}} call. As a result, this type becomes a
> regular, user type, and does not map to a corresponding type on the Java side.
> * Add test that combines QueryEntity with AffinityKey
> * Check that other system types (IgniteUuid, etc) don't have this problem,
> add tests
> * Make sure we never overwrite system types during registration
> * Improve examples tests: Thick Sql example provides inconsistent output due
> to this bug
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
