Clarify the data retention policy for topic and partitions (#949)

apache · Aug 8, 2024 · 138eadd · 138eadd
1 parent dd81d1b
commit 138eadd
Show file tree

Hide file tree

Showing 7 changed files with 7 additions and 7 deletions.
diff --git a/docs/cookbooks-retention-expiry.md b/docs/cookbooks-retention-expiry.md
@@ -65,7 +65,7 @@ For more information on the two parameters, refer to the [`broker.conf`](referen
 
 ### Set retention policy
 
-You can set a retention policy for a namespace by specifying the namespace, a size limit and a time limit in `pulsar-admin`, REST API and Java.
+You can set a retention policy for a namespace by specifying the namespace, a size limit and a time limit in `pulsar-admin`, REST API and Java. And all the non-partitioned topics and topic partitions will apply the specified data retention policy for the namespace unless you overwrite the data retention policy for the specific topic by using topic level policies.
 
 ````mdx-code-block
 <Tabs groupId="api-choice"

diff --git a/versioned_docs/version-2.10.x/cookbooks-retention-expiry.md b/versioned_docs/version-2.10.x/cookbooks-retention-expiry.md
@@ -65,7 +65,7 @@ For more information of the two parameters, refer to the [`broker.conf`](referen
 
 ### Set retention policy
 
-You can set a retention policy for a namespace by specifying the namespace, a size limit and a time limit in `pulsar-admin`, REST API and Java.
+You can set a retention policy for a namespace by specifying the namespace, a size limit and a time limit in `pulsar-admin`, REST API and Java. And all the non-partitioned topics and topic partitions will apply the specified data retention policy for the namespace unless you overwrite the data retention policy for the specific topic by using topic level policies.
 
 ````mdx-code-block
 <Tabs

diff --git a/versioned_docs/version-2.11.x/cookbooks-retention-expiry.md b/versioned_docs/version-2.11.x/cookbooks-retention-expiry.md
@@ -64,7 +64,7 @@ For more information on the two parameters, refer to the [`broker.conf`](referen
 
 ### Set retention policy
 
-You can set a retention policy for a namespace by specifying the namespace, a size limit and a time limit in `pulsar-admin`, REST API and Java.
+You can set a retention policy for a namespace by specifying the namespace, a size limit and a time limit in `pulsar-admin`, REST API and Java. And all the non-partitioned topics and topic partitions will apply the specified data retention policy for the namespace unless you overwrite the data retention policy for the specific topic by using topic level policies.
 
 ````mdx-code-block
 <Tabs groupId="api-choice"

diff --git a/versioned_docs/version-3.0.x/cookbooks-retention-expiry.md b/versioned_docs/version-3.0.x/cookbooks-retention-expiry.md
@@ -64,7 +64,7 @@ For more information on the two parameters, refer to the [`broker.conf`](referen
 
 ### Set retention policy
 
-You can set a retention policy for a namespace by specifying the namespace, a size limit and a time limit in `pulsar-admin`, REST API and Java.
+You can set a retention policy for a namespace by specifying the namespace, a size limit and a time limit in `pulsar-admin`, REST API and Java. And all the non-partitioned topics and topic partitions will apply the specified data retention policy for the namespace unless you overwrite the data retention policy for the specific topic by using topic level policies.
 
 ````mdx-code-block
 <Tabs groupId="api-choice"

diff --git a/versioned_docs/version-3.1.x/cookbooks-retention-expiry.md b/versioned_docs/version-3.1.x/cookbooks-retention-expiry.md
@@ -64,7 +64,7 @@ For more information on the two parameters, refer to the [`broker.conf`](referen
 
 ### Set retention policy
 
-You can set a retention policy for a namespace by specifying the namespace, a size limit and a time limit in `pulsar-admin`, REST API and Java.
+You can set a retention policy for a namespace by specifying the namespace, a size limit and a time limit in `pulsar-admin`, REST API and Java. And all the non-partitioned topics and topic partitions will apply the specified data retention policy for the namespace unless you overwrite the data retention policy for the specific topic by using topic level policies.
 
 ````mdx-code-block
 <Tabs groupId="api-choice"

diff --git a/versioned_docs/version-3.2.x/cookbooks-retention-expiry.md b/versioned_docs/version-3.2.x/cookbooks-retention-expiry.md
@@ -65,7 +65,7 @@ For more information on the two parameters, refer to the [`broker.conf`](referen
 
 ### Set retention policy
 
-You can set a retention policy for a namespace by specifying the namespace, a size limit and a time limit in `pulsar-admin`, REST API and Java.
+You can set a retention policy for a namespace by specifying the namespace, a size limit and a time limit in `pulsar-admin`, REST API and Java. And all the non-partitioned topics and topic partitions will apply the specified data retention policy for the namespace unless you overwrite the data retention policy for the specific topic by using topic level policies.
 
 ````mdx-code-block
 <Tabs groupId="api-choice"

diff --git a/versioned_docs/version-3.3.x/cookbooks-retention-expiry.md b/versioned_docs/version-3.3.x/cookbooks-retention-expiry.md
@@ -65,7 +65,7 @@ For more information on the two parameters, refer to the [`broker.conf`](referen
 
 ### Set retention policy
 
-You can set a retention policy for a namespace by specifying the namespace, a size limit and a time limit in `pulsar-admin`, REST API and Java.
+You can set a retention policy for a namespace by specifying the namespace, a size limit and a time limit in `pulsar-admin`, REST API and Java. And all the non-partitioned topics and topic partitions will apply the specified data retention policy for the namespace unless you overwrite the data retention policy for the specific topic by using topic level policies.
 
 ````mdx-code-block
 <Tabs groupId="api-choice"