[
https://issues.apache.org/jira/browse/IGNITE-5383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044203#comment-16044203
]
Vyacheslav Daradur commented on IGNITE-5383:
--------------------------------------------
[~vozerov]
There are small difference
[pr.ci.tests|http://ci.ignite.apache.org/viewLog.html?buildId=654943] as
compared to
[master.ci.tests|http://ci.ignite.apache.org/viewLog.html?buildId=656066].
I think they aren't related to changes.
Diffs:
[Ignite SPI (4
new)|http://ci.ignite.apache.org/viewLog.html?buildId=654928&tab=buildResultsDiv&buildTypeId=IgniteTests_IgniteSpi]
[Ignite Basic (2
new)|http://ci.ignite.apache.org/viewLog.html?buildId=654855&tab=buildResultsDiv&buildTypeId=IgniteTests_IgniteBasic]
> Do not perform cache key validation when BinaryMarshaller is used
> -----------------------------------------------------------------
>
> Key: IGNITE-5383
> URL: https://issues.apache.org/jira/browse/IGNITE-5383
> Project: Ignite
> Issue Type: Task
> Components: binary, cache
> Affects Versions: 2.1
> Reporter: Vladimir Ozerov
> Assignee: Vyacheslav Daradur
> Labels: important
> Fix For: 2.1
>
>
> Currently whenever cache operation is performed, we invoke
> {{GridCacheAdapter.validateCacheKey}} to make sure that key overrides
> {{equals}} and {{hashCode}}.
> This check should not be performed when {{BinaryMarshaller}} is set, since we
> do not use these methods in binary mode.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
