[
https://issues.apache.org/jira/browse/IGNITE-29197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18130984#comment-18130984
]
Zhang Zhenhao commented on IGNITE-29197:
----------------------------------------
PR submitted: apache/ignite#13737
> Binary key deserialization masks the error when put follows invoke in a
> transaction
> -----------------------------------------------------------------------------------
>
> Key: IGNITE-29197
> URL: https://issues.apache.org/jira/browse/IGNITE-29197
> Project: Ignite
> Issue Type: Bug
> Reporter: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-2
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Calling `put()` after `invoke()` for the same key in the same transaction is
> rejected by Ignite. However, `GridNearTxLocal.enlistWriteEntry()` constructs
> the error message using:
> {code}
> throw new IgniteCheckedException("Failed to enlist write value for key
> (cannot have update value in " +
> "transaction after EntryProcessor is applied): " + CU.value(cacheKey,
> cacheCtx, false));
> {code}
> If the key builts wiotout a java class, this attempts to deserialize the key
> and gets the execution during deserialization:
> {noformat}
> Caused by: class org.apache.ignite.binary.BinaryInvalidTypeException:
> <KEY_TYPE>
> {noformat}
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
