Hi everyone!

Been working with Pulsar for a few years now, but this is my first message on 
this list.

I’ve been playing around locally with a patch set for allowing one to configure 
on a broker/namespace/topic level if the TTL should be applied to subscriptions 
and replicators that are active.

The motivation was that we have users that occasionally need to re-consume 
historic events (within the retention policy) that are older than the TTL. They 
do this by moving the cursor of their subscription backwards in time but then 
get frustrated when the TTL gets applied and the cursor skips forward 
“underneath” their consumer.
Temporarily disabling the TTL on the topic works as a workaround, but it is 
cumbersome, especially as the team needing it done often isn’t the team with 
permissions to modify policies on the topic.
By allowing the `checkMessageExpiry()` function to skip subscriptions that are 
active we’d be able to leave the TTL policy in place which ensures that old 
messages get expired properly for inactive subscriptions, while at the same 
time not changing the state underneath active consumers.
The default configuration would naturally be the current behaviour.

So basically, my main question is this:

Should I go ahead and make a PIP for this and clean it up for contributing, or 
would it be a waste of time since it’d be undesirable as an option and would be 
rejected anyway?


Additionally, if I were to clean this up for contribution; would you like 
separate toggles for ordinary subscriptions, replicators and shadow replicators?


Best regards
[LEGO]
Ulrik Boll Djurtoft

Sr. IT Engineer
Event Streaming Platform

Mobile
+45 52211505
E-mail
[email protected]<mailto:[email protected]>
LEGO System A/S

Aastvej 1
7190 Billund
Denmark

www.LEGO.com<https://www.lego.com/>

LEGO and the LEGO logo are trademarks of the LEGO Group. ©2026 The LEGO Group.
This email message contains confidential information and is intended only for 
the individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and delete 
this e-mail from your system.

Reply via email to