I fixed the problem, it was a bug actually. By default classes which has some custom Java logic (e.g. Externalizable, or with writeObject/readObject methods) will be written using OptimizedMarshaller, so similar field names is not a problem. If you want to serialize such class in binary format and have duplicate field names, you should provide your own BinarySerializer, which will write these fields with different names.
On Fri, Dec 18, 2015 at 8:07 PM, Andrey Kornev <[email protected]> wrote: > How am I supposed to handle this situation if the class comes from a 3d > party I can't modify? > > Thanks > Andrey > > > Date: Fri, 18 Dec 2015 09:12:22 +0300 > > Subject: Re: CacheEntry serialization failure > > From: [email protected] > > To: [email protected] > > > > I'll take a look. > > > > On Fri, Dec 18, 2015 at 4:37 AM, Valentin Kulichenko < > > [email protected]> wrote: > > > > > Folks, > > > > > > It looks like CacheEntry implementation (i.e., the entry that contains > > > version) can't be properly serialized with the BinaryMarshaller. I > created > > > the test and the ticket: > https://issues.apache.org/jira/browse/IGNITE-2203 > > > > > > Can someone take a look? > > > > > > -Val > > > > >
