This is an automated email from the ASF dual-hosted git repository.
junma pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git
The following commit(s) were added to refs/heads/main by this push:
new 687238116d5 Add note for using non-persistent topic in TableView (#358)
687238116d5 is described below
commit 687238116d552cb063be9f14642f3dfb2bc1984c
Author: Kai Wang <[email protected]>
AuthorDate: Mon Jan 9 13:55:35 2023 +0800
Add note for using non-persistent topic in TableView (#358)
---
docs/client-libraries-java.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/client-libraries-java.md b/docs/client-libraries-java.md
index dc22cd41889..4060b1c346c 100644
--- a/docs/client-libraries-java.md
+++ b/docs/client-libraries-java.md
@@ -1107,7 +1107,7 @@ With TableView, Pulsar clients can fetch all the message
updates from a topic an
:::note
Each TableView uses one Reader instance per partition, and reads the topic
starting from the compacted view by default. It is highly recommended to enable
automatic compaction by [configuring the topic compaction
policies](cookbooks-compaction.md#configure-compaction-to-run-automatically)
for the given topic or namespace. More frequent compaction results in shorter
startup times because less data is replayed to reconstruct the TableView of the
topic.
-
+Starting from Pulsar 2.11.0, TableView also supports reading non-persistent
topics, but it does not guarantee data consistency.
:::
The following figure illustrates the dynamic construction of a TableView
updated with newer values of each key.
@@ -1305,4 +1305,4 @@ Assume that you want to connect Pulsar client 1 to
cluster A.
</TabItem>
</Tabs>
-````
\ No newline at end of file
+````
