Thin client before version 2.9 throws an exception when there is more than one scheme with the same type name and compact footers are enabled. The scheme is a set of field names of the object, so, using only one scheme per type (if it's possible in your case) will solve the problem. If you don't want to update Ignite server, you can update only thin client, it will also solve the problem.
пн, 22 нояб. 2021 г. в 12:57, Naveen Kumar <naveen.band...@gmail.com>: > Thanks Alex.. > Here it says it throws this exception when ignite does not find this record > In our case, data exists and it get resolved if we do a node restart > > And, any work-around we have to fix this issue with current version > ignite 2.8.1 > > Thanks > > On Mon, Nov 22, 2021 at 12:20 PM Alex Plehanov <plehanov.a...@gmail.com> > wrote: > >> Hello! >> >> Most probably it's related to ticket [1] that is fixed in 2.9 release. >> >> [1]: https://issues.apache.org/jira/browse/IGNITE-13192 >> >> пн, 22 нояб. 2021 г. в 03:11, Naveen Kumar <naveen.band...@gmail.com>: >> >>> Hi All >>> >>> We are using 2.8.1 >>> At times, we do get this BinaryObjectException while calling GETs thru >>> thin client, we dont see any errors or exceptions on node logs, this only >>> be seen on the cline tside. >>> what could be the potential reason for this >>> >>> Attached the exact error message >>> >>> >>> >>> >>> Thanks >>> >>> -- >>> Thanks & Regards, >>> Naveen Bandaru >>> >> > > -- > Thanks & Regards, > Naveen Bandaru >
