I'd like to discuss the current behavior before making a decision.
First, note that it's currently valid for an exclusive consumer to
call `acknowledge` on an individual message. `reconsumeLater` is
essentially just `send` with a delay then `acknowledge`.
Second, the RetryTopicTest#testRetryTopic
> They can use `reconsumeLaterCumulative ` for non shared sub instead
It means this is a breaking change. Users have to be noticed during
upgrading.
IMO, what we have to be clear is if we should insist on message
order delivery
with the default exclusive subscription type. If it's true, we would
They can use `reconsumeLaterCumulative ` for non shared sub instead
On 2022/07/26 02:06:05 Haiting Jiang wrote:
> Hi Gavin,
>
> Do we have any plans for compatibility issue? As the exclusive subscription
> type
> is the default setting, user may use it even if they don't have any message
> o
Hi Gavin,
Do we have any plans for compatibility issue? As the exclusive subscription type
is the default setting, user may use it even if they don't have any message
order
requirements.
Thanks,
Haiting
On 2022/07/25 06:50:12 Gavin gao wrote:
> As The official doc says "Currently, retry
As The official doc says "Currently, retry letter topic is enabled in
Shared subscription types". But, actually We can use this method when using
non shared sub.We should disable using this method for message order
considering.
Pr: https://github.com/apache/pulsar/pull/16745
