Thank you, Thomas. That clears my confusions. :)
Shen
On Tue, Apr 25, 2017 at 7:30 PM, Thomas Groh
wrote:
> getCurrentTimestamp returns the timestamp of the current element. Both
> Bounded and Unbounded Readers have this method.
>
> For a bounded source, this is safe
getCurrentTimestamp returns the timestamp of the current element. Both
Bounded and Unbounded Readers have this method.
For a bounded source, this is safe - the source watermark can be held to
negative infinity while elements remain in the source and advance to
infinity after all elements are
You want to use an existing source but just change the watermark tracking?
You can't do this in your pipeline right now, but you could probably easily
wrap a source and proxy every method except getWatermark, though I have
never tried.
The general feature that might address this is discussed a
Hi,
Can application developers provide classes/methods to specify how to
generate watermarks from sources, and how to aggregate watermarks from
multiple input PCollections? Say, emit at most 1 watermark per second, or
create watermarks that are 5 seconds older than the latest tuple's
timestamp?