Re: [DISCUSS] PIP 26: Delayed Message Delivery

2018-11-22 Thread Sijie Guo
FYI. I copied the content of this PIP to wiki - https://github.com/apache/pulsar/wiki/PIP-26%3A-Delayed-Message-Delivery On Sun, Nov 11, 2018 at 6:11 AM Jia Zhai wrote: > Thanks a lot. > +1 for Pulsar Function way > > On Sun, Nov 11, 2018 at 3:51 PM Sijie Guo wrote: > > > Jia, > > > > I think w

Re: [DISCUSS] PIP 26: Delayed Message Delivery

2018-11-11 Thread Jia Zhai
Thanks a lot. +1 for Pulsar Function way On Sun, Nov 11, 2018 at 3:51 PM Sijie Guo wrote: > 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 Disp

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

Re: [DISCUSS] PIP 26: Delayed Message Delivery

2018-11-09 Thread wenfeng wang
Joe +1 Joe F 于2018年11月10日周六 下午12:47写道: > I am not a fan of adding complexity to the dispatch path, and I will always > have serious concerns about proposals that do so, including this one. > > In general, I would prefer Pulsar to keep the dispatch path simple and > efficient, and avoid server s

Re: [DISCUSS] PIP 26: Delayed Message Delivery

2018-11-09 Thread Joe F
I am not a fan of adding complexity to the dispatch path, and I will always have serious concerns about proposals that do so, including this one. In general, I would prefer Pulsar to keep the dispatch path simple and efficient, and avoid server side implementations of business logic. Streaming at

[DISCUSS] PIP 26: Delayed Message Delivery

2018-11-08 Thread 李鹏辉gmail
Dear all This is a PIP to add feature of delayed message delivery. ## Motivation Scheduled and delayed message delivery is a very common feature to support in a message system. Basically individual message can have a header which will be set by publisher and based on the header value the broker