Hi Gordon, Thanks for your reply / help.
Yes, following the savepoint road would certainly make the job, even it's complicating the picture. We might go that way in the future, but so far, we have followed an easier one through eventual consistency: * if some referential data is not (yet) loaded (as part of the join), then do not join ;-) (a) instead of doing a regular join (as expected), just set "not found" for the missing property values and push (through the collector) the produced data to the next tasks, (b) store the incomplete data in some state, and when referential data has come, then make the regular join, and push updated data to the next taks (through the collector). So, it's all about eventual consistency. Thanks. Regards, Dominique Le mar. 28 janv. 2020 à 03:43, Tzu-Li Tai <tzuli...@gmail.com> a écrit : > Hi Dominique, > > FLIP-17 (Side Inputs) is not yet implemented, AFAIK. > > One possible way to overcome this right now if your reference data is > static > and not continuously changing, is to use the State Processor API to > bootstrap a savepoint with the reference data. > Have you looked into that and see if it would work for you? > > Cheers, > Gordon > > > > -- > Sent from: > http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/ >
