ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Kukushkin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-5795) @AffinityKeyMapped ignored if QueryEntity used
Date Mon, 04 Sep 2017 16:35:02 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-5795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152789#comment-16152789
] 

Alexey Kukushkin commented on IGNITE-5795:
------------------------------------------

Good point, will update Ignite public docs and close the ticket.

> @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
>              Labels: usability
>             Fix For: 2.3
>
>
> 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
(v6.4.14#64029)

Mime
View raw message