[jira] [Updated] (IGNITE-5795) @AffinityKeyMapped ignored if QueryEntity used

["Alexey Kukushkin (JIRA)" <ji...@apache.org>]

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

Alexey Kukushkin updated IGNITE-5795:
-------------------------------------
    Fix Version/s:     (was: 2.5)
                   2.6

> @AffinityKeyMapped ignored if QueryEntity used
> ----------------------------------------------
>
>                 Key: IGNITE-5795
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5795
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>    Affects Versions: 2.0
>            Reporter: Dmitry Karachentsev
>            Assignee: Alexey Kukushkin
>            Priority: Major
>              Labels: usability
>             Fix For: 2.6
>
>
> When cache configured with QueryEntity and used key type with @AffinityKeyMapped field, it will be ignored and wrong partition calculated. This happens because QueryEntity processing precedes key type registering in binary meta cache. On that step CacheObjectBinaryProcessorImpl#affinityKeyField called and unable to resolve type, so null returned and null putted in affKeyFields.
> On next put/get operation CacheObjectBinaryProcessorImpl#affinityKeyField will return null from affKeyFields, but should be affinity key field.
> Test that reproduces problem in [PR 2330|https://github.com/apache/ignite/pull/2330]
> To wrorkaround the issue, set IgniteConfiguration#setKeyConfiguration(), it will force registering key.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)