I've created ticket according with the observations: https://issues.apache.org/jira/browse/IGNITE-14886

However, WA would be to preregister all the types on the system start, this might possibly be done using lifecycle beans or right after the start before allowing the applications to proceed with the load. The root cause is the CREATE TABLE statement that is using the same type, which creates this type with different schema that needs updates to be made to existing binary schemas when the binary object builder is invoked within EntryProcessor.

Best regards,
Anton

 

From: VeenaMithare
Sent: Tuesday, April 27, 2021 3:46 PM
To: user@ignite.apache.org
Subject: 2.8.1 : CacheEntryProcessor for insert/update within Transaction supported ?

 

Hi Team,

 

Is the functionality to use CacheEntryProcessor for insert/update within

Transaction supported ?

 

As mentioned in this post, insert of a record using cacheentryprocessor

always fails with UnregisteredBinaryTypeException if the insert is done

within a transaction :

 

http://apache-ignite-users.70518.x6.nabble.com/Right-Handling-of-UnRegisteredBinaryObjectTypeException-tp35412p35681.html

 

regards,

Veena.

 

 

 

 

 

 

 

--

Sent from: http://apache-ignite-users.70518.x6.nabble.com/

 

Reply via email to