Got it, if you serialized with a given builder once, this type will be cached globally in the internal cache. So the behaviour you observe is expected and correct: you can change schema dynamically, but you have to preserve compatibility. This means that you can change and remove fields, but not their type, because object type is not expected to be bound to a given cache. Serialized object can be stored and used in other ways e.g. stored in other caches or a client node is using outdated schema is trying to deserialize the object.
So you have to create new binary type or add a field with different name. Or do a complete restart with cleanup. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
