You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexander Paschenko (JIRA)" <ji...@apache.org> on 2016/08/05 15:20:20 UTC

[jira] [Updated] (IGNITE-3633) Throw an exception when binary object without explicitly set hash code is used as a key

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

Alexander Paschenko updated IGNITE-3633:
----------------------------------------
    Summary: Throw an exception when binary object without explicitly set hash code is used as a key  (was: Throw an exception when an object without explicitly set hash code)

> Throw an exception when binary object without explicitly set hash code is used as a key
> ---------------------------------------------------------------------------------------
>
>                 Key: IGNITE-3633
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3633
>             Project: Ignite
>          Issue Type: Task
>          Components: binary, cache, SQL
>            Reporter: Alexander Paschenko
>            Assignee: Alexander Paschenko
>             Fix For: 1.8
>
>
> New binary built keys erroneously get put to cache as having cache code of 0. We want to force user to set hash code explicitly by throwing an exception when they do not do so.
> Proposed solution by Denis Magda:
> http://apache-ignite-developers.2346864.n4.nabble.com/All-BinaryObjects-created-by-BinaryObjectBuilder-stored-at-the-same-partition-by-default-td8042i20.html



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