Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify the data retention policy for topic and partitions #949

Merged
merged 1 commit into from
Aug 8, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/cookbooks-retention-expiry.md
Original file line number Diff line number Diff line change
Expand Up @@ -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"
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -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"
Expand Down
2 changes: 1 addition & 1 deletion versioned_docs/version-3.0.x/cookbooks-retention-expiry.md
Original file line number Diff line number Diff line change
Expand Up @@ -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"
Expand Down
2 changes: 1 addition & 1 deletion versioned_docs/version-3.1.x/cookbooks-retention-expiry.md
Original file line number Diff line number Diff line change
Expand Up @@ -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"
Expand Down
2 changes: 1 addition & 1 deletion versioned_docs/version-3.2.x/cookbooks-retention-expiry.md
Original file line number Diff line number Diff line change
Expand Up @@ -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"
Expand Down
2 changes: 1 addition & 1 deletion versioned_docs/version-3.3.x/cookbooks-retention-expiry.md
Original file line number Diff line number Diff line change
Expand Up @@ -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"
Expand Down
Loading