Anonymitaet commented on code in PR #699: URL: https://github.com/apache/pulsar-site/pull/699#discussion_r1320765024
########## docs/cookbooks-retention-expiry.md: ########## @@ -36,7 +37,7 @@ Pulsar's [admin interface](admin-api-overview.md) enables you to manage both ret By default, when a Pulsar message arrives at a broker, the message is stored until it has been acknowledged on all subscriptions, at which point it is marked for deletion. You can override this behavior and retain messages that have already been acknowledged on all subscriptions by setting a *retention policy* for all topics in a given namespace. Retention is based on both a *size limit* and a *time limit*. The diagram below illustrates the concept of message retention. - + Review Comment: ```suggestion  ``` ########## docs/cookbooks-message-queue.md: ########## @@ -2,6 +2,7 @@ id: cookbooks-message-queue title: Use Pulsar as a message queue sidebar_label: "Message queue" +description: Learn to use Pulsar as a message queue. Review Comment: ```suggestion description: Learn how to use Pulsar as a message queue. ``` ########## docs/tutorials-produce-consume.md: ########## @@ -2,6 +2,7 @@ Id: tutorials-produce-consume title: Produce and consume messages sidebar_label: "Produce and consume messages" +description: Learn to produce and consume messages in Pulsar. Review Comment: ```suggestion description: Learn how to produce and consume messages in Pulsar. ``` ########## docs/tutorials-tenant.md: ########## @@ -2,14 +2,15 @@ Id: tutorials-tenant title: How to set up a tenant sidebar_label: "Set up a tenant" +description: Learn to set up a tenant in Pulsar. Review Comment: ```suggestion description: Learn how to set up a tenant in Pulsar. ``` ########## docs/tutorials-namespace.md: ########## @@ -2,6 +2,7 @@ Id: tutorials-namespace title: Create a namespace sidebar_label: "Create a namespace" +description: Learn to create and verify a namespace in Pulsar. Review Comment: ```suggestion description: Learn how to create and verify a namespace in Pulsar. ``` ########## docs/cookbooks-retention-expiry.md: ########## @@ -350,7 +351,7 @@ By default, Pulsar stores all unacknowledged messages forever. This can lead to The TTL parameter is like a stopwatch attached to each message that defines the amount of time a message is allowed to stay unacknowledged. When the TTL expires, Pulsar automatically moves the message to the acknowledged state (and thus makes it ready for deletion). The diagram below illustrates the concept of TTL. - + Review Comment: ```suggestion  ``` ########## docs/cookbooks-retention-expiry.md: ########## @@ -188,7 +189,7 @@ admin.namespaces().getRetention(namespace); You can control the allowable size and/or time of backlogs, at the namespace level, using *backlog quotas*. Pulsar uses a quota to enforce a hard limit on the logical size of the backlogs in a topic. Backlog quota triggers an alert policy (for example, producer exception) once the quota limit is reached. The diagram below illustrates the concept of backlog quota. - + Review Comment: ```suggestion  ``` ########## docs/tutorials-topic.md: ########## @@ -2,6 +2,7 @@ Id: tutorials-topic title: How to create a topic sidebar_label: "Create a topic" +description: Learn to create a topic in Pulsar. Review Comment: ```suggestion description: Learn how to create a topic in Pulsar. ``` -- 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]
