Jason918 opened a new issue #13756: URL: https://github.com/apache/pulsar/issues/13756
This issue is created to track the process of the serial topic policy optimization with `HierarchyTopicPolicies`. ## Motivation Update topic policy with HierarchyTopicPolicies comes with these benefits: - All topic policy related settings will goes into AbstractTopic#topicPolicies, easier to understand, check, review, and modify. - Unify policy update to AbstractTopic. And easier to find which policy is not applied to non-persistent topic yet. And we can easily add support for it. - Unify policy value with 3 level settings (topic/namespace/broker), and priority with topic > namespace > broker. And it's easier to find which level settings is missing. - All values are updated at creation or by trigger. We can save some resource to update it or recalculate each time we use it. - etc. ### Progress - [ ] backLogQuotaMap - [ ] subscriptionTypesEnabled - [ ] replicationClusters - [ ] deduplicationEnabled - [ ] messageTTLInSeconds - [ ] maxProducerPerTopic - [ ] maxConsumerPerTopic - [ ] maxConsumersPerSubscription - [ ] maxUnackedMessagesOnConsumer - [ ] maxUnackedMessagesOnSubscription - [ ] delayedDeliveryTickTimeMillis - [ ] delayedDeliveryEnabled - [ ] inactiveTopicPolicies - [ ] dispatchRate - [ ] subscriptionDispatchRate - [ ] compactionThreshold - [ ] publishRate - [ ] subscribeRate - [ ] deduplicationSnapshotIntervalSeconds - [ ] maxMessageSize - [ ] maxSubscriptionsPerTopic - [ ] replicatorDispatchRate These topic policies can not apply to this optimization because it's used for ML and before `Topic` creation. - offloadPolicies - persistence - retentionPolicies -- 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]
