[
https://issues.apache.org/jira/browse/IGNITE-29245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikita Amelchev updated IGNITE-29245:
-------------------------------------
Fix Version/s: 2.19
> Fix thin client putAllConflict/removeAllConflict ignoring keepBinary on the
> server
> ----------------------------------------------------------------------------------
>
> Key: IGNITE-29245
> URL: https://issues.apache.org/jira/browse/IGNITE-29245
> Project: Ignite
> Issue Type: Bug
> Reporter: Nikita Amelchev
> Assignee: Nikita Amelchev
> Priority: Critical
> Fix For: 2.19
>
>
> A thin client sends putAllConflict/removeAllConflict with the keepBinary
> flag, but since IGNITE-28348 the server
> handles them without it: ClientCacheRequest#internalCache obtains the
> internal cache through
> IgniteCacheProxy#internalProxy(), which drops the withKeepBinary() applied to
> the public proxy.
> Because of that, the primary node deserializes the values when
> CacheVersionConflictResolver compares them. On a CDC
> destination cluster fed by a thin client streamer the value classes are
> usually not deployed, so the resolver fails
> with BinaryInvalidTypeException, the transaction commit ends with a heuristic
> failure and the failure handler stops
> the node.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
