Re: union followed by timestamp assignment / watermark generation

2017-06-15 Thread Aljoscha Krettek
Hi, Yes, I can’t think of cases right now where placing the extractor after a union makes sense. In general, I think it’s always best to place the timestamp extractor as close to the sources (or in the sources, for Kafka) as possible. Right now it would be quite hard (and probably a bit hacky)

Re: union followed by timestamp assignment / watermark generation

2017-06-15 Thread Petr Novotnik
Hello Aljoscha, Fortunately, I found the program in Google's caches :) I've attached below for reference. I'm stunned by how accurately you have hit the point given the few pieces of information I left in the original text. +1 Yes, it's exactly as you explained. Can you think of a scenario where

Re: union followed by timestamp assignment / watermark generation

2017-06-14 Thread Aljoscha Krettek
Hi Petr, I just stumbled across this (slightly older) mail. Your example on pastebin is not available anymore but I’m guessing you have roughly these two topologies: 1. Source1 -> Map1 -> ExtractTimestamps -| | -> Map3 … Source

union followed by timestamp assignment / watermark generation

2017-05-06 Thread Petr Novotnik
Hello Flinkers, Given this small example program: > https://pastebin.com/30JbbgpH I'd expect the output: > one|three > two|four However, I consistently receive ... > one > two|four ... due to "three" being considered a late-comer which then gets discarded. When I remove `assignTimestampsAndW