Vladislav Pyatkov created IGNITE-29197:
------------------------------------------
Summary: 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
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)
