ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3191) BinaryObjectBuilder: binary schema id depends on the order of fields addition
Date Wed, 01 Jun 2016 09:01:10 GMT

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

Vladimir Ozerov commented on IGNITE-3191:
-----------------------------------------

{{TreeMap}} is slower than {{LinkedHashMap}}, and we didn't consider many distinct field combinations
as a common use case.

Moreover, even now I don't understand well why we should bother with changing everything from
unordered to ordered structure.

> BinaryObjectBuilder: binary schema id depends on the order of fields addition
> -----------------------------------------------------------------------------
>
>                 Key: IGNITE-3191
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3191
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Denis Magda
>             Fix For: 1.7
>
>
> Presently if an object is created using BinaryObjectBuilder then several BinarySchemes
can be generated for the same set of fields in case when fields are added in a different order.
> This happens because {{LinkedHashMap}} is used underneath. However we should rely on
order-free structure like {{TreeMap}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message