Timestamped-based synchronized reads from multiple input topics?

2019-07-02 Thread Adam Bellemare
Hi All The use-case is pretty simple. Lets say we have a history of events with the following: key=userId, value = (timestamp, productId) and we want to remap it to: key=productId, value=(original_timestamp, userId) Now, say I have 30 days of backlog, and 2 input topics with the original events.

Slack digest for #dev - 2019-07-02

2019-07-02 Thread Apache Pulsar Slack
2019-07-01 17:28:12 UTC - Vineeth Thumma: @Vineeth Thumma has joined the channel 2019-07-01 22:18:13 UTC - Guillaume Rosauro: @Guillaume Rosauro has joined the channel 2019-07-02 06:14:13 UTC - Jiayi Liao: @Jiayi Liao has joined the channel

[RESULT] [VOTE] Pulsar Release 2.4.0 Candidate 2

2019-07-02 Thread PengHui Li
The vote is now closed for Pulsar Release 2.4.0 Release Candidate 2 with 11 +1 (4 +1 binding votes) votes, 0 +0/-0 votes, 0 -1 votes. 4 +1 bindings are: Jerry Peng Jia Zhai Rajan Dhabalia Sijie Guo 7 +1 non-bindings are: Eren Avsarogullari Fangbin Sun Guangning E Penghui Li Xiaolong

Re: [VOTE] Pulsar Release 2.4.0 Candidate 2

2019-07-02 Thread Sijie Guo
Moved the vote result to dev@ mailing list. - Sijie On Tue, Jul 2, 2019 at 1:01 PM Jerry Peng wrote: > +1 Binding LGTM > > Validated by following from validation guide: > > - Pulsar standalone > - Create tenant and namespace > - Create function > - Publish and consume message > - Stateful Funct