Okay, sounds very reasonable :)
On Thu, Apr 30, 2015 at 10:15 PM, Stephan Ewen wrote:
> For the variant with the "run()" method, this requires strong assumptions
> about the internal behavior of the source.
>
> Unless I am overlooking something, the source needs to guarantee this:
>
> - It need
For the variant with the "run()" method, this requires strong assumptions
about the internal behavior of the source.
Unless I am overlooking something, the source needs to guarantee this:
- It needs to lock internally and perform the state update and record emit
call inside the locked scope
-
Hi,
The only thing we need is to guarantee that the source will not output any
records or update the state while we take the snapshot and send the
barrier. There are multiple ways of doing this I guess. We could simply
lock on these objects for instance or add the methods you wrote. If we
lock, we
Hi all!
I think we need to change the interface of the streaming source function.
The function currently has simply a run() method where it does its work,
until canceled.
With this, it is hard to write sources, where the state and the snapshot
barriers are exactly aligned.
When performing the ch
