Thanks for the follow-up and the bug report, David.
We're taking a look at that.
On Mon, Oct 10, 2016 at 4:36 PM, David Garcia wrote:
> Thx for the responses. I was able to identify a bug in how the times are
> obtained (offsets resolved as unknown cause the issue):
>
> “Actually, I think th
Thx for the responses. I was able to identify a bug in how the times are
obtained (offsets resolved as unknown cause the issue):
“Actually, I think the bug is more subtle. What happens when a consumed topic
stops receiving messages? The smallest timestamp will always be the static
timestamp
> We have run the application (and have confirmed data is being received)
for over 30 mins…with a 60-second timer.
Ok, so your app does receive data but punctuate() still isn't being called.
:-(
> So, do we need to just rebuild our cluster with bigger machines?
That's worth trying out. See
htt
Yeah, this is possible. We have run the application (and have confirmed data
is being received) for over 30 mins…with a 60-second timer. So, do we need to
just rebuild our cluster with bigger machines?
-David
On 10/7/16, 11:18 AM, "Michael Noll" wrote:
David,
punctuate() is sti
David,
punctuate() is still data-driven at this point, even when you're using the
WallClock timestamp extractor.
To use an example: Imagine you have configured punctuate() to be run every
5 seconds. If there's no data being received for a minute, then punctuate
won't be called -- even though you
