Hi, I’ve opened a new PIP to discuss:
Currently, in Pulsar, we have a configuration named `subscriptionExpirationTimeMinutes` to manage the subscription expiration of `PersistentTopic` and `NonPersistentTopic`. When we set a value which is greater than 0 to `subscriptionExpirationTimeMinutes`, it will affect both `PersistentTopic` and `NonPersistentTopic`. Their inactive subscriptions will get expired and will clean automatically. For `NonPersistentTopic`, its subscriptions can be clean because we don't guarantee its data integrity. But for `PersistentTopic`, if we clean its subscriptions automatically may lead to data loss. However, their subscription expiration is managed by the same configuration(`subscriptionExpirationTimeMinutes`), we can't manage their subscription expiration independently. So I want to introduce a new configuration named `nonPersistentSubscriptionExpirationTimeMinutes` to manage `NonPersistentTopic`'s subscription expiration. Please feel free to leave your comments, the PIP link: https://github.com/apache/pulsar/issues/19448 <https://github.com/apache/pulsar/issues/19448> Thanks, Tao Jiuming
