Hi Anton, Please find a sample project with one of the 'unregisteredbinarytypeexception' . The readme.txt is present in the attached zip.
TestProject.zip <http://apache-ignite-users.70518.x6.nabble.com/file/t2757/TestProject.zip> As mentioned in the readme.txt , the behaviour noticed is as below : 1. Run the UpdateClientNotWorking - insert of a record through entry processor doesnt work. 2. Run the UpdateClientWorking - insert of a record through entry processor works. This is because we do a dummy registration of metadata on the client side before the entryprocessor is invoked within the transaction. Questions are as below : 1. Why does the entry processor run in the client side ? As per the definition of entry processor - it is used to execute updates on entries on the nodes that store it . TestProject.zip https://ignite.apache.org/docs/latest/distributed-computing/collocated-computations#entry-processor 2. Because of point 1, when we execute a transaction of say 1000 records, we need to give a huge timeout value - since most of the time of the transaction is spent in the client execution of the entry processor . Is there any workaround for this ? regards, Veena. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
