You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by hj...@apache.org on 2019/06/27 04:32:21 UTC
[pulsar] branch master updated: Update for admin part (#4605)
This is an automated email from the ASF dual-hosted git repository.
hjf 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 93b7b93 Update for admin part (#4605)
93b7b93 is described below
commit 93b7b9303f78c2f6e335e0c27d0ea7a01ac975da
Author: Jennifer Huang <47...@users.noreply.github.com>
AuthorDate: Thu Jun 27 12:32:14 2019 +0800
Update for admin part (#4605)
---
site2/docs/functions-runtime.md | 15 +++++++--------
site2/docs/functions-worker.md | 3 ++-
2 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/site2/docs/functions-runtime.md b/site2/docs/functions-runtime.md
index 5a57026..a603c60 100644
--- a/site2/docs/functions-runtime.md
+++ b/site2/docs/functions-runtime.md
@@ -1,29 +1,28 @@
---
id: functions-runtime
title: Configure Functions runtime
-sidebar_label: Configure Functions runtime
+sidebar_label: Admin: Configure Functions runtime
---
+This guide is used for administrator.
-Currently, Pulsar Functions support the following three methods to run functions.
+Pulsar Functions support the following methods to run functions.
- *Thread*: Invoke functions in threads in Functions Worker.
- *Process*: Invoke functions in processes forked by Functions Worker.
- *Kubernetes*: Submit functions as Kubernetes StatefulSets by Functions Worker.
## Configure thread runtime
-
-*Thread* runtime is easy to configure. In most cases, you don't need to configure anything. You can customize the thread group name with the following settings:
+It is easy to configure *Thread* runtime. In most cases, you do not need to configure anything. You can customize the thread group name with the following settings:
```yaml
threadContainerFactory:
threadGroupName: "Your Function Container Group"
```
-*Thread* runtime only supports Java language.
+*Thread* runtime is only supported in Java function.
## Configure process runtime
-
-Similar as *Thread* runtime, you don't need to configure anything special when enabling *Process* runtime.
+When you enable *Process* runtime, you do not need to configure anything.
```yaml
processContainerFactory:
@@ -37,7 +36,7 @@ processContainerFactory:
extraFunctionDependenciesDir:
```
-Currently Pulsar supports running Java, Python, and Go Functions in process runtime mode.
+*Process* runtime is supported in Java, Python, and Go functions.
## Configure Kubernetes runtime
diff --git a/site2/docs/functions-worker.md b/site2/docs/functions-worker.md
index 0f20a6d..a42572f 100644
--- a/site2/docs/functions-worker.md
+++ b/site2/docs/functions-worker.md
@@ -1,8 +1,9 @@
---
id: functions-worker
title: Deploy and manage functions worker
-sidebar_label: Functions Worker
+sidebar_label: Admin: Pulsar Functions Worker
---
+This guide is used for administrator.
Pulsar `functions-worker` is a logic component to run Pulsar Functions in cluster mode. Two options are available, and you can select either of the two options based on your requirements.
- [run with brokers](#run-Functions-worker-with-brokers)