Hi Nuno, Because of this, we have a legacy structure that I showed before. Could you probably include more information about this legacy structure you mentioned here in this mail thread? I couldn’t find any other reference to that. That could be helpful to understanding your use case more here.
- Gordon On 15 September 2017 at 12:59:15 PM, nragon (nuno.goncal...@wedotechnologies.com) wrote: Hi, First of all, great #FF17, really enjoyed it. After attending some of the dataArtisans folks talks, realized that serialization should be optimized if there is no way to use supported objects. In my case, users can configure their source in our application online which gives them freedom to dynamically change the number and type of attributes. Moreover, between operator the object can be changed in terms of number of attributes. Because of this, we have a legacy structure that I showed before. Should I implement my own TypeInformation, TypeComparator, TypeSerializer and TypeInfoFactory? Am I forgetting something? Thanks, Nuno -- Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
