This is an automated email from the ASF dual-hosted git repository.
sijie pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git
The following commit(s) were added to refs/heads/master by this push:
new d1545bd [Doc] Fixed a typo in Cookbook / Topic compaction (#4544)
d1545bd is described below
commit d1545bda987e676c8b95aea86436146453573e72
Author: Daniel Andersson <[email protected]>
AuthorDate: Tue Jun 18 19:34:24 2019 +0200
[Doc] Fixed a typo in Cookbook / Topic compaction (#4544)
## Motivation
Improving the quality of the documentation.
---
site2/docs/cookbooks-compaction.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/site2/docs/cookbooks-compaction.md
b/site2/docs/cookbooks-compaction.md
index 0a8f8ac..006c08f 100644
--- a/site2/docs/cookbooks-compaction.md
+++ b/site2/docs/cookbooks-compaction.md
@@ -17,7 +17,7 @@ To use compaction:
## When should I use compacted topics? {#when}
-The classic example of a topic that could benefit from compaction would be a
stock ticker topic through which consumers can access up-to-date values for
specific stocks. Imagine a scneario in which messages carrying stock value data
use the stock symbol as the key (`GOOG`, `AAPL`, `TWTR`, etc.). Compacting this
topic would give consumers on the topic two options:
+The classic example of a topic that could benefit from compaction would be a
stock ticker topic through which consumers can access up-to-date values for
specific stocks. Imagine a scenario in which messages carrying stock value data
use the stock symbol as the key (`GOOG`, `AAPL`, `TWTR`, etc.). Compacting this
topic would give consumers on the topic two options:
* They can read from the "original," non-compacted topic in case they need
access to "historical" values, i.e. the entirety of the topic's messages.
* They can read from the compacted topic if they only want to see the most
up-to-date messages.
