Re: Apache ignite evolvable object
Hello! Binarylizable may be shorter but BinaryObject supports evolvable objects, as in, you can add new fields, and cache operations will usually preserve these. You will only lose these when you de-serialize your object to old version of POJO, but most of internal operations (such as rebalancing) will not touch them. Regards, -- Ilya Kasnacheev сб, 2 мая 2020 г. в 13:50, Hemambara : > Does it save additional bytes by default or do we have to implement > binarylable, if so do you have any example. > > If it does by default, does that mean, let's say if I send data from new > version node to old version node and send the same data back to new version > node will it preserve thos new fields?? > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
Re: Apache ignite evolvable object
Does it save additional bytes by default or do we have to implement binarylable, if so do you have any example. If it does by default, does that mean, let's say if I send data from new version node to old version node and send the same data back to new version node will it preserve thos new fields?? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Apache ignite evolvable object
Hi, BinaryObjects allow doing this: https://apacheignite.readme.io/docs/binary-marshaller Evgenii пт, 1 мая 2020 г. в 09:03, Hemambara : > I am using apache ignite 2.8.0. Looking for an option to have evolvable > data > model similar to coherence (com.tangosol.io.Evolvable). Do we have any ? > Idea is to save future data if the domain model version is backward > compatible and when the same model is transferred to new version, we can > retrieve fields from future data, with out any data loss > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
Apache ignite evolvable object
I am using apache ignite 2.8.0. Looking for an option to have evolvable data model similar to coherence (com.tangosol.io.Evolvable). Do we have any ? Idea is to save future data if the domain model version is backward compatible and when the same model is transferred to new version, we can retrieve fields from future data, with out any data loss -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
