mattisonchao opened a new pull request, #21231: URL: https://github.com/apache/pulsar/pull/21231
### Motivation https://github.com/apache/pulsar/pull/7817 Introduced topic-level policy for a managed-config with the bug. which can lead to an inconsistent data retention policy If the pulsar topic policy service isn't initialized. plus, https://github.com/apache/pulsar/pull/19368 get a policy from the cache directly making this situation worse. ### Modifications - Avoid getting topic policy directly in the broker service. It will leave potential bugs by inconsistent topic policies. - Deprecate some methods by undefined exceptions and blocking calls. - AbstractTopic#getTopicPolicies(); - BrokerService#getTopicPolicies(TopicName topicName); - Let BrokerService#isAllowAutoSubscriptionCreationAsync use async method to get topic policies. - Let BrokerService#getManagedLedgerConfig use async method to get topic policies. ### Verifying this change - [x] Make sure that the change passes the CI checks. ### Documentation <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. --> - [ ] `doc` <!-- Your PR contains doc changes. --> - [ ] `doc-required` <!-- Your PR changes impact docs and you will update later --> - [x] `doc-not-needed` <!-- Your PR changes do not impact docs --> - [ ] `doc-complete` <!-- Docs have been already added --> -- 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: commits-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
