Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Thu, 11 Aug 2016 20:25:20 +0000 (UTC)
From: "Denis Magda (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.12995235.1470409717000.286421.1470947120441@Atlassian.JIRA>
In-Reply-To: <JIRA.12995235.1470409717000@Atlassian.JIRA>
References: <JIRA.12995235.1470409717000@Atlassian.JIRA> <JIRA.12995235.1470409717394@arcas>
Subject: [jira] [Commented] (IGNITE-3633) Throw an exception when binary
 object without explicitly set hash code is used as a key
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 11 Aug 2016 20:25:22 -0000


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

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

[~al.psc], I left my review notes in the pull-request.

Please consider them.

> 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)