You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Kuznetsov (JIRA)" <ji...@apache.org> on 2017/05/10 03:06:04 UTC

[jira] [Closed] (IGNITE-4485) CacheJdbcPojoStore returns unexpected BinaryObject upon loadCache()

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

Alexey Kuznetsov closed IGNITE-4485.
------------------------------------

> CacheJdbcPojoStore returns unexpected BinaryObject upon loadCache()
> -------------------------------------------------------------------
>
>                 Key: IGNITE-4485
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4485
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 2.0
>            Reporter: Alexandr Kuramshin
>            Assignee: Alexey Kuznetsov
>              Labels: easyfix
>             Fix For: 2.0
>
>
> When calling loadCache(IgniteBiInClosure clo, Object... args) sometimes we get unexpected values of type BinaryObject in IgniteBiInClosure.apply(), whereas POJO value kind was registered previously for well known key type.
> It's so because getOrCreateCacheMappings returns HashMap which resorts entity mappings for the same key but with different value kind. When BinaryMarshaller is used, then this map contains two mappings for the same key - POJO and BINARY.
> Possible fix is to use LinkedHashMap, then POJO mapping will be picked first.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)