[pulsar-site] branch main updated: Docs sync done from apache/pulsar (#bf29a4b)

[ur...@apache.org]

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

urfree 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 a96aaef0bd6 Docs sync done from apache/pulsar (#bf29a4b)
a96aaef0bd6 is described below

commit a96aaef0bd617f2a47e80db2184ee986b6226b70
Author: github-actions[bot] <41...@users.noreply.github.com>
AuthorDate: Sun Dec 11 01:36:46 2022 +0000

    Docs sync done from apache/pulsar (#bf29a4b)
---
 .../docs/administration-load-balance.md            |  7 +++++
 site2/website-next/docs/helm-deploy.md             |  3 ---
 .../reference/next/pulsar-admin/namespaces.md      | 30 ++++++++++++++++++++++
 3 files changed, 37 insertions(+), 3 deletions(-)

diff --git a/site2/website-next/docs/administration-load-balance.md b/site2/website-next/docs/administration-load-balance.md
index 6de9b3b5561..c31cb88cf2f 100644
--- a/site2/website-next/docs/administration-load-balance.md
+++ b/site2/website-next/docs/administration-load-balance.md
@@ -58,6 +58,13 @@ Since the load for the topics in a bundle might change over time and predicting
 Pulsar supports the following two bundle split algorithms:
 * `range_equally_divide`: split the bundle into two parts with the same hash range size.
 * `topic_count_equally_divide`: split the bundle into two parts with the same number of topics.
+* `specified_positions_divide`: split the bundle into several parts by the specified positions.
+
+:::tip
+
+* The `specified_positions_divide` algorithms only support use by admin API and do not support set into `defaultNamespaceBundleSplitAlgorithm`.
+
+:::
 
 To enable bundle split, you need to configure the following settings in the `broker.conf` file, and set `defaultNamespaceBundleSplitAlgorithm` based on your needs.
 
diff --git a/site2/website-next/docs/helm-deploy.md b/site2/website-next/docs/helm-deploy.md
index dff0ab03aec..fa03409b241 100644
--- a/site2/website-next/docs/helm-deploy.md
+++ b/site2/website-next/docs/helm-deploy.md
@@ -47,9 +47,6 @@ By default, the Pulsar Helm Chart creates Volume Claims with the expectation tha
 ```yaml
 volumes:
   persistence: true
-  # configure the components to use local persistent volume
-  # the local provisioner should be installed prior to enable local persistent volume
-  local_storage: false
 ```
 
 :::note
diff --git a/site2/website-next/static/reference/next/pulsar-admin/namespaces.md b/site2/website-next/static/reference/next/pulsar-admin/namespaces.md
index 183104b4bff..3993128b977 100644
--- a/site2/website-next/static/reference/next/pulsar-admin/namespaces.md
+++ b/site2/website-next/static/reference/next/pulsar-admin/namespaces.md
@@ -217,6 +217,36 @@ $ pulsar-admin namespaces revoke-subscription-permission options
 | `-r, --role` | Client role to which revoke permissions|null||
 
 
+## <em>get-subscription-permission-required</em>
+
+Get whether a namespace requires explicit permission to consume from a subscription when no permission is defined.
+
+**Command:**
+
+```shell
+$ pulsar-admin namespaces get-subscription-permission-required options
+```
+
+
+
+## <em>set-subscription-permission-required</em>
+
+Set whether a role requires explicit permission to consume from a subscription that has no subscription permission defined in the namespace.
+
+**Command:**
+
+```shell
+$ pulsar-admin namespaces set-subscription-permission-required options
+```
+
+**Options:**
+
+|Flag|Description|Default|
+|---|---|---|
+| `--disable, -d` | Disable message encryption required|false||
+| `--enable, -e` | Enable message encryption required|false||
+
+
 ## <em>set-clusters</em>
 
 Set replication clusters for a namespace