Re: [DISCUSS] PIP 26: Delayed Message Delivery

2018-11-10 Thread Sijie Guo
Jia, I think what Joe suggested is to implement this outside of broker. The currrent design doesn’t have to change, but the logic is implemented in a Pulsar function - we can call it “Delayed Dispatch Function”. It basically takes one topic as input topic, dispatch the messages to the output topic

Re: [DISCUSS] PIP 26: Delayed Message Delivery

2018-11-10 Thread Dave Fisher
I think Joe left a clue in the idea of using Pulsar Functions. Sent from my iPhone > On Nov 10, 2018, at 6:26 PM, Jia Zhai wrote: > > Thanks Joe for the comments. > To implementation this feature in client side is great, but from my view, > to achieve "Delayed Message", we may have to touch the

Re: [DISCUSS] PIP 26: Delayed Message Delivery

2018-11-10 Thread Jia Zhai
Thanks Joe for the comments. To implementation this feature in client side is great, but from my view, to achieve "Delayed Message", we may have to touch the dispatch path. Is there any idea or suggestion of how to do it from client side? On Sat, Nov 10, 2018 at 3:41 PM wenfeng wang wrote: > Jo

Slack digest for #dev - 2018-11-10

2018-11-10 Thread Apache Pulsar Slack
2018-11-09 12:48:13 UTC - Chris Miller: I just sent a pull request that adds a unit test, highlighting what appears to be a bug in JSONSchema. I don't understand the JSONSchema logic well enough to offer a fix though sorry 2018-11-09 15:12:32 UTC