You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by mm...@apache.org on 2019/03/19 17:41:50 UTC
[pulsar] branch master updated: update partition doc (#3846)
This is an automated email from the ASF dual-hosted git repository.
mmerli 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 4fe7ab4 update partition doc (#3846)
4fe7ab4 is described below
commit 4fe7ab4f4fea4c50dfea70bf323a9db5358012e0
Author: Jia Zhai <zh...@apache.org>
AuthorDate: Wed Mar 20 01:41:46 2019 +0800
update partition doc (#3846)
---
site2/docs/admin-api-partitioned-topics.md | 5 +----
.../versioned_docs/version-2.3.0}/admin-api-partitioned-topics.md | 8 +++-----
2 files changed, 4 insertions(+), 9 deletions(-)
diff --git a/site2/docs/admin-api-partitioned-topics.md b/site2/docs/admin-api-partitioned-topics.md
index d86a256..0f68523 100644
--- a/site2/docs/admin-api-partitioned-topics.md
+++ b/site2/docs/admin-api-partitioned-topics.md
@@ -113,10 +113,7 @@ than the existing number.
Decrementing the number of partitions would deleting the topic, which is not supported in Pulsar.
-Already created partitioned producers and consumers can’t see newly created partitions and
-it requires to recreate them at application so, newly created producers and consumers can connect
-to newly added partitions as well. Therefore, it can violate partition ordering at producers until
-all producers are restarted at application.
+Already created partitioned producers and consumers will automatically find the newly created partitions.
#### pulsar-admin
diff --git a/site2/docs/admin-api-partitioned-topics.md b/site2/website/versioned_docs/version-2.3.0/admin-api-partitioned-topics.md
similarity index 97%
copy from site2/docs/admin-api-partitioned-topics.md
copy to site2/website/versioned_docs/version-2.3.0/admin-api-partitioned-topics.md
index d86a256..5518b1c 100644
--- a/site2/docs/admin-api-partitioned-topics.md
+++ b/site2/website/versioned_docs/version-2.3.0/admin-api-partitioned-topics.md
@@ -1,7 +1,8 @@
---
-id: admin-api-partitioned-topics
+id: version-2.3.0-admin-api-partitioned-topics
title: Managing partitioned topics
sidebar_label: Partitioned topics
+original_id: admin-api-partitioned-topics
---
@@ -113,10 +114,7 @@ than the existing number.
Decrementing the number of partitions would deleting the topic, which is not supported in Pulsar.
-Already created partitioned producers and consumers can’t see newly created partitions and
-it requires to recreate them at application so, newly created producers and consumers can connect
-to newly added partitions as well. Therefore, it can violate partition ordering at producers until
-all producers are restarted at application.
+Already created partitioned producers and consumers will automatically find the newly created partitions.
#### pulsar-admin