[
https://issues.apache.org/jira/browse/IGNITE-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15411799#comment-15411799
]
ASF GitHub Bot commented on IGNITE-3633:
----------------------------------------
GitHub user alexpaschenko opened a pull request:
https://github.com/apache/ignite/pull/928
IGNITE-3633 GridCacheUtils - validate hash code presence in binary objs.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-3633
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/928.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #928
----
commit ef90e78d90551f025f41ef334061bfdf63f97ec1
Author: Alexander Paschenko <[email protected]>
Date: 2016-08-08T13:21:36Z
IGNITE-3633 GridCacheUtils - validate hash code presence in binary objects
----
> 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)
