Skip to content

Commit

Permalink
Correct version issue
Browse files Browse the repository at this point in the history
Not valid from 2.6.0 

Thanks @gaoran10

> We introduce topic-level policies from 2.6.0, refer to apache/pulsar#4955, but I think we support retention policies at the topic level from 2.7.0, refer to apache/pulsar#7747.

>Make the default value of the configuration topicLevelPoliciesEnabled as true from 2.11.0, refer to apache/pulsar#15619.
  • Loading branch information
AlvaroStream authored Jun 28, 2023
1 parent db5331e commit 747e874
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion versioned_docs/version-3.0.x/concepts-messaging.md
Original file line number Diff line number Diff line change
Expand Up @@ -1073,7 +1073,7 @@ Pulsar has two features, however, that enable you to override this default behav
:::tip
All message retention and expiry are managed at the [namespace](#namespaces) level or at topic level from Pulsar `2.6.0` activating `topicLevelPoliciesEnabled=true` at broker.conf. Since `2.11` that default value is `true`. For a how-to, see the [Message retention and expiry](cookbooks-retention-expiry.md) cookbook.
All message retention and expiry are managed at the [namespace](#namespaces) level or at topic level from Pulsar `2.7.0` activating `topicLevelPoliciesEnabled=true` at broker.conf. Since `2.11` that default value is `true`. For a how-to, see the [Message retention and expiry](cookbooks-retention-expiry.md) cookbook.
:::
Expand Down

0 comments on commit 747e874

Please sign in to comment.