tjiuming opened a new issue, #17673: URL: https://github.com/apache/pulsar/issues/17673
### Search before asking - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Motivation Currently, Pulsar only supports global offload auto trigger policy: `managedLedgerOffloadAutoTriggerSizeThresholdBytes` and `managedLedgerOffloadTimeThresholdInSeconds`(see: https://github.com/apache/pulsar/pull/17398), this is a very coarse granularity. For the purpose of more fine control of auto trigger offload, we'd better to support namespace/topic level auto trigger offload policy. ### Solution Add the following configurations: ``` // Namespace -> managedLedger size private final Map<String, Long> managedLedgerOffloadNamespaceSizeThresholdBytes; // Topic -> managedLedger size private final Map<String, Long> managedLedgerOffloadTopicSizeThresholdBytes; // Namespace -> time threshold in seconds private final Map<String, Long> managedLedgerOffloadNamespaceTimeThresholdSeconds; // Topic -> time threshold in seconds private final Map<String, Long> managedLedgerOffloadTopicTimeThresholdSeconds; ``` ### Alternatives _No response_ ### Anything else? _No response_ ### Are you willing to submit a PR? - [X] I'm willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
