You could try using JSON for all your data, this might me slow, however. The other route, which I would suggest, is to have your own custom TypeSerializers than can efficiently deal with different types and dynamic schemas.
Cheers, Aljoscha On Thu, 5 Jan 2017 at 07:02 ljwagerfield <lawre...@dmz.wagerfield.com> wrote: > I should add: the operators determine how to handle each message by > inspecting the message's SCHEMA_ID field (every message has a SCHEMA_ID as > its first field). > > > > -- > View this message in context: > http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Are-heterogeneous-DataStreams-possible-tp10852p10853.html > Sent from the Apache Flink User Mailing List archive. mailing list archive > at Nabble.com. >
