Hello all,

I am extremely apologies about the discussion hours. It was my first time
to have discussions and voting process and wasn’t aware about the policy.

Will keep this in mind from next time.

Once again apologies.

Sincere
Nitin Goyal

On Tue, 10 Jan 2023 at 10:04 PM, Dave Fisher <[email protected]> wrote:

> -1 (binding) because the discussion thread is in progress and most
> important you only allowed for 71 hours of discussion.
>
> I think it is important that any change to the main producer / consumer
> flow be proven to have no performance regressions in the broker.
>
> Regards,
> Dave
>
> > On Jan 8, 2023, at 11:35 PM, Enrico Olivelli <[email protected]>
> wrote:
> >
> > I am sure that this is a good idea.
> >
> > -1 (binding)
> >
> > I will follow up on the discussion thread
> >
> > I am sorry I am catching up late on this thread
> >
> > Enrico
> >
> > Il giorno lun 9 gen 2023 alle ore 03:51 Ran Gao <[email protected]> ha
> scritto:
> >>
> >> +1 (non-binding)
> >>
> >> Thanks,
> >> Ran Gao
> >>
> >> On 2023/01/08 15:05:31 Zixuan Liu wrote:
> >>> +1 (non-binding)
> >>>
> >>> Thanks,
> >>> Zixuan
> >>>
> >>> Yunze Xu <[email protected]> 于2023年1月8日周日 22:38写道:
> >>>
> >>>> +1 (binding)
> >>>>
> >>>> Thanks,
> >>>> Yunze
> >>>>
> >>>> On Sun, Jan 8, 2023 at 4:46 PM Zike Yang <[email protected]> wrote:
> >>>>>
> >>>>> +1 (non-binding)
> >>>>>
> >>>>> Thanks,
> >>>>> Zike Yang
> >>>>>
> >>>>> On Sun, Jan 8, 2023 at 3:22 PM Haiting Jiang <[email protected]
> >
> >>>> wrote:
> >>>>>>
> >>>>>> +1 binding
> >>>>>>
> >>>>>> Although I think we should use more unique keys for system
> properties
> >>>> in pulsar,
> >>>>>> e.g. reserve all properties prefixed with "PULSAR_" for system
> >>>> internal usage.
> >>>>>> But it's another topic as we already have "RECONSUMETIMES".
> >>>>>>
> >>>>>>
> >>>>>> On Sun, Jan 8, 2023 at 12:27 PM Nitin Goyal <
> [email protected]>
> >>>> wrote:
> >>>>>>>
> >>>>>>> Hello community,
> >>>>>>>
> >>>>>>> I'm starting the VOTE for PIP-239: Retry Mechanism per Message
> title.
> >>>>>>>
> >>>>>>> Motivation: We are working on a project where each message has
> their
> >>>> retry
> >>>>>>> as per the requirements. like one message 100 times and other
> >>>> messages 5
> >>>>>>> times and so on. This feature also adds an extra functionality
> while
> >>>>>>> comparing existing queueing services like RabbitMQ or SQS etc.
> >>>>>>>
> >>>>>>> For more details please find the detailed PIP at:
> >>>>>>> https://github.com/apache/pulsar/issues/19136
> >>>>>>>
> >>>>>>> Discussion Threads:
> >>>>>>> 1.
> https://lists.apache.org/thread/rn6114xxtx1j57yy2jbmdv4xzt80o1hz
> >>>>>>> 2.
> https://lists.apache.org/thread/b9rfv6t307z439xx3zt2ym4p140qzp06
> >>>>>>>
> >>>>>>> Proposed changes in pulsar go client library.
> >>>>>>> https://github.com/apache/pulsar-client-go/pull/939
> >>>>>>>
> >>>>>>> Thanks
> >>>>>>> Nitin Goyal
> >>>>
> >>>
>
> --
Regards
Nitin Goyal

Reply via email to