[pulsar.wiki] branch master updated: Updated PIP 34: Add new subscribe type Key_shared (markdown)

[pe...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

penghui pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.wiki.git


The following commit(s) were added to refs/heads/master by this push:
     new 1fe9bf5  Updated PIP 34: Add new subscribe type Key_shared (markdown)
1fe9bf5 is described below

commit 1fe9bf57146766634d0d65d1639d09f9f28d013d
Author: lipenghui <pe...@apache.org>
AuthorDate: Thu Mar 19 10:31:46 2020 +0800

    Updated PIP 34: Add new subscribe type Key_shared (markdown)
---
 PIP-34:-Add-new-subscribe-type-Key_shared.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/PIP-34:-Add-new-subscribe-type-Key_shared.md b/PIP-34:-Add-new-subscribe-type-Key_shared.md
index 74b24e3..db89b29 100644
--- a/PIP-34:-Add-new-subscribe-type-Key_shared.md
+++ b/PIP-34:-Add-new-subscribe-type-Key_shared.md
@@ -1,8 +1,9 @@
 
- * **Status**: Accepted
+ * **Status**: Implemented
  * **Author**: Jia Zhai
  * **Pull Request**: https://github.com/apache/pulsar/pull/4079
  * **Mailing List discussion**:
+ * **Release**: 2.4.0
 
 ## Motivation
 At present, there are 3 kinds of subscription modes: exclusive, shared, and failover. Shared mode subscription is used a lot, because consumers could effectively parallel consume messages of same partition.  But using shared mode will not keep the message order of same key, It would be good to leverage share mode, while also keeping the ordering of messages.