ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Denis Magda (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3633) Throw an exception when binary object without explicitly set hash code is used as a key
Date Mon, 15 Aug 2016 17:57:20 GMT

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

Denis Magda commented on IGNITE-3633:
-------------------------------------

Alexander,

At the moment PR contains changes spread out across 67 files. Looks like you need to back
merge something so that non your changes are filtered out.

> 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: Denis Magda
>             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)

Mime
View raw message