Let's imagine the following scenario. We have a queue (distributed in a cluster and partitioned) with a persistent storage. We add Person ( name : String ) to it. Then, because of business requirements we will add another field let's say address which is also o String. What options do we have to do data migration to support new model and be backwards compatible ?
Possible options that I found : 1. Create a new queue and migrate data programatically - the application will use the new queue. 2. Store data in another format let's say JSON and provide backwards compatibility at code level. 3. Is possible to use inheritance, but then we will have versioning in model which is not desirable. I think this problem arises also in the context of in memory queues. Do you have other idea ? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
