Re: [DISCUSSION] Delayed message delivery

On Thu, Jan 24, 2019 at 8:13 AM Joe F wrote: > To me this discussion presupposes that a streaming system should provide > a service like a database. Before we discuss about how to implement this, > we should look at whether this is something that fits into what is the core > of Pulsar. I stil

Re: [DISCUSSION] Delayed message delivery

To me this discussion presupposes that a streaming system should provide a service like a database. Before we discuss about how to implement this, we should look at whether this is something that fits into what is the core of Pulsar. I still have the same concerns against doing this in the brok

Re: [DISCUSSION] Delayed message delivery

Hi all, Since this discussion have a lot of edges, I propose the following: Maybe can we make a vote or some sort of decision about what we are going to decide next? For example, I would left for a future discussion the topic of arbitrary delay for each message because is a more difficult to achi

Slack digest for #dev - 2019-01-24

2019-01-23 19:54:02 UTC - Prasanna kumar Krishnamurthy: @Prasanna kumar Krishnamurthy has joined the channel

Build failed in Jenkins: pulsar-website-build #534

See Changes: [github] Fix race condition: broker not scheduling read for active consumer [guosijie] Add a running flag for Kafka source connector (#3310) -- [...trunca