2020-06-22 11:10:24 UTC - Charvak Patel: It doesnt solve the issue of the 
clients being stuck after topic creation. Once I figure that out will submit
----
2020-06-22 14:55:30 UTC - matt_innerspace.io: if i subscribe to multiple topics 
for a single function, how do 'processing guarantees' affect message delivery?  
it seems if i subscribe as a window function with 'at least once', and one 
topic misses a message, and it appears later, the window generates the 'group 
message' again later.  Are there rules here somewhere?
----
2020-06-22 16:14:39 UTC - Devin G. Bost: Thanks for clarifying that.
----
2020-06-22 16:16:15 UTC - Devin G. Bost: Thanks for the report on this.
----
2020-06-22 16:16:34 UTC - Devin G. Bost: @Addison Higham Have you experienced 
any other issues with 2.5.2 so far?
----
2020-06-22 16:17:41 UTC - Devin G. Bost: Or, did you guys roll back to 2.5.1? 
(If so, have you experienced any issues on 2.5.1?)
----
2020-06-22 16:20:12 UTC - Addison Higham: We stayed on 2.5.2 + a patch or two, 
I think that was the main issue we but we also monkey patched in one other 
small fix that raised a timeout in getting the managedLedgerConfig in broker 
service, I don't think it is necessary, but it is there
+1 : Devin G. Bost
----
2020-06-22 23:53:50 UTC - Devin G. Bost: I’ve never tried using Pulsar 
functions for windowing operations. Maybe we’re thinking of two different 
things here, but whenever I need complex event processing, Flink is my go-to. 
Pulsar + Flink = very powerful
----
2020-06-22 23:54:15 UTC - Devin G. Bost: Not sure exactly how the Pulsar 
delivery semantics are at play in your situation though.
----
2020-06-22 23:54:58 UTC - Devin G. Bost: I didn’t even know that you could 
window with Pulsar functions…
----
2020-06-22 23:55:47 UTC - Devin G. Bost: Has anyone tried adding a date stamp 
to the Pulsar log4j logs? Not having a date in the logs is extremely annoying. 
I’m tempted to create a PR just for that change.
----

Reply via email to