You could do something with reflection ... I have played with (by monkey-patching in ruby) deserializing fields in structs that I didn't know about and then re-serializing it. I do not at this time have authorization to share this, but it is doable.
On Sat, May 24, 2014 at 11:49 AM, Klaus Kraft <[email protected]> wrote: > Hi all, > > so far I gained some experiences with Apache Avro and Google ProtoBuf. Now > I wanted to play around with Thrift a bit. > One of the thrings I'm mainly interested in is data migration. Lets say I > have defined certain structs. > I know that thrift can deal with additions, deletions and renamings. > > But can I also deal with more complex migration scenarios, e.g., when I > move a field of a struct > into another struct? Or splitting a field of a struct into two fields (of > the same struct)? > The crucial point here is to be able to write migration classes or so which > prevent me from > loosing data. > > In ProtoBuf, I could write a message dynamically. This allowed me to create > a message with > certain content at runtime. This was based on some reflection mechanisms. > Is something like this > also possible in Thrift? Can I write a message dynamically at runtime > without using the > classes generated out of the .thrift file? > > Thanks in advance. >
