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

Ignite TC Bot commented on IGNITE-29245:
----------------------------------------

{panel:title=Branch: [pull/13781/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13781/head] Base: [master] : New Tests 
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Thin Client: Java{color} [[tests 
2|https://ci2.ignite.apache.org/viewLog.html?buildId=9466749]]
* {color:#013220}ClientTestSuite: thin.ThinClientPutAllConflictKeepBinaryTest - 
PASSED{color}
* {color:#013220}ClientTestSuite: 
ThinClientPutAllConflictKeepBinaryTest.testKeepBinary - PASSED{color}

{panel}
[TeamCity *--> Run :: All* 
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9466808&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9466808 
rerunBuildIds=none{color}

> 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
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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)

Reply via email to