You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/11/06 19:03:59 UTC
[jira] [Closed] (IGNITE-4085) Binary objects: Do not use
BinaryField when comparing objects with the same schema.
[ https://issues.apache.org/jira/browse/IGNITE-4085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov closed IGNITE-4085.
-----------------------------------
> Binary objects: Do not use BinaryField when comparing objects with the same schema.
> -----------------------------------------------------------------------------------
>
> Key: IGNITE-4085
> URL: https://issues.apache.org/jira/browse/IGNITE-4085
> Project: Ignite
> Issue Type: Task
> Components: binary
> Affects Versions: 1.7
> Reporter: Vladimir Ozerov
> Labels: performance
> Fix For: 1.8
>
>
> It is not efficient to use {{BinaryField.value}} directly when comparing binary objects because it leads to "materialization" of the field.
> Instead, when well-known type is met, we should simply find field start in both objects and perform usual byte-by-byte comparison.
> E.g., for string it will be:
> 1) Find position
> 2) Compare lengths (readInt)
> 3) Compare contents byte-by-byte.
> The same goes for other types:
> 1) Primitive arrays
> 2) UUID
> 3) Data/TimeStamp.
> Please ensure that byte-by-byte comparison is performed efficiently, e.g. that we compare bigger chunks (e.g. 8 bytes at once).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)