-
Notifications
You must be signed in to change notification settings - Fork 420
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge remote-tracking branch 'upstream/master' into support_schemales…
…s_decode
- Loading branch information
Showing
8 changed files
with
302 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -337,3 +337,26 @@ This section configures the portable plugin runtime. | |
## Ruleset Provision | ||
|
||
Support file based stream and rule provisioning on startup. Users can put a [ruleset](../api/restapi/ruleset.md#ruleset-format) file named `init.json` into `data` directory to initialize the ruleset. The ruleset will only be import on the first startup of eKuiper. | ||
|
||
## Configure FoundationDB as storage | ||
|
||
eKuiper uses sqlite by default to store some meta-information. At the same time, eKuiper also supports using FoundationDB as meta-storage data. We can achieve this through the following steps: | ||
|
||
* Confirm that the environment where eKuiper is located has installed and started FoundationDB, and confirm the storage path used by FoundationDB. Please refer to [Official Document](https://apple.github.io/foundationdb/administration.html#default-cluster-file) | ||
* Confirm the APIVersion of the fdb c language library used by the eKuiper host, and replace the eKuiper dependent library with the corresponding version. Taking APIVersion 6.2.0 as an example, execute the following command in the eKuiper home directory: | ||
|
||
```shell | ||
go get github.com/apple/foundationdb/bindings/[email protected] | ||
``` | ||
|
||
* Execute `make build_with_fdb` to compile kuiperd | ||
* Modify the configuration as follows: | ||
|
||
```yaml | ||
store: | ||
#Type of store that will be used for keeping state of the application | ||
type: fdb | ||
extStateType: fdb | ||
fdb: | ||
path: <path-of-fdb-cluster-file> | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -324,3 +324,26 @@ SQL 中的 [get_keyed_state](../sqls/functions/other_functions.md#getkeyedstate) | |
## 初始化规则集 | ||
|
||
支持基于文件的流和规则的启动时配置。用户可以将名为 `init.json` 的[规则集](../api/restapi/ruleset.md#规则集格式)文件放入 `data` 目录,以初始化规则集。该规则集只在eKuiper 第一次启动时被导入。 | ||
|
||
## 配置 FoundationDB 作为存储 | ||
|
||
eKuiper 默认使用 sqlite 来存储一些元信息,同时 eKuiper 也支持使用 FoundationDB 来作为元存储数据,我们可以通过以下步骤实现: | ||
|
||
* 确认 eKuiper 所在环境已经安装并启动 FoundationDB,并确认 FoundationDB 所使用的存储 Path. 可参考[官方文档](https://apple.github.io/foundationdb/administration.html#default-cluster-file) | ||
* 确认 eKuiper 宿主机所使用的 fdb c 语言库的 APIVersion 版本,并将 eKuiper 依赖库替换为相应版本,以 APIVersion 6.2.0 为例,在 eKuiper 主目录执行以下命令: | ||
|
||
```shell | ||
go get github.com/apple/foundationdb/bindings/[email protected] | ||
``` | ||
|
||
* 执行 `make build_with_fdb` 编译 kuiperd | ||
* 在配置中按照如下修改: | ||
|
||
```yaml | ||
store: | ||
#Type of store that will be used for keeping state of the application | ||
type: fdb | ||
extStateType: fdb | ||
fdb: | ||
path: <path-of-fdb-cluster-file> | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters