This is an automated email from the ASF dual-hosted git repository.
wayne pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-horaedb-docs.git
The following commit(s) were added to refs/heads/main by this push:
new 9f49aed chore: more rename to horaedb (#115)
9f49aed is described below
commit 9f49aedfe716be37c98193ed89cbde940d49e5f8
Author: chunshao.rcs <[email protected]>
AuthorDate: Mon Dec 25 17:00:14 2023 +0800
chore: more rename to horaedb (#115)
---
README-CN.md | 6 +-
README.md | 6 +-
docs/book.toml | 3 +-
docs/src/cn/about.md | 6 +-
docs/src/cn/cluster_deployment/no_meta.md | 4 +-
docs/src/cn/cluster_deployment/with_meta.md | 55 +--
docs/src/cn/design/architecture.md | 32 +-
docs/src/cn/design/table_partitioning.md | 6 +-
docs/src/cn/dev/compile_run.md | 2 +-
docs/src/cn/dev/crate-deps.dot | 89 -----
docs/src/cn/dev/crate-deps.svg | 415 ---------------------
docs/src/cn/dev/platform.md | 14 +-
docs/src/cn/dev/profiling.md | 8 +-
docs/src/cn/ecosystem/opentsdb.md | 2 +-
docs/src/cn/operation/observability.md | 6 +-
docs/src/cn/operation/system_table.md | 5 +-
docs/src/cn/operation/table.md | 2 +-
docs/src/cn/quick_start.md | 16 +-
docs/src/cn/sdk/go.md | 26 +-
docs/src/cn/sdk/java.md | 10 +-
docs/src/cn/sdk/python.md | 10 +-
docs/src/cn/sdk/rust.md | 22 +-
docs/src/cn/sql/dml/insert.md | 2 +-
docs/src/en/about.md | 6 +-
docs/src/en/cluster_deployment/no_meta.md | 4 +-
docs/src/en/cluster_deployment/with_meta.md | 57 +--
docs/src/en/design/architecture.md | 32 +-
docs/src/en/design/table_partitioning.md | 6 +-
docs/src/en/dev/compile_run.md | 2 +-
docs/src/en/dev/conventional_commit.md | 2 +-
docs/src/en/dev/crate-deps.dot | 89 -----
docs/src/en/dev/crate-deps.svg | 415 ---------------------
docs/src/en/dev/platform.md | 14 +-
docs/src/en/dev/profiling.md | 8 +-
docs/src/en/ecosystem/opentsdb.md | 2 +-
docs/src/en/operation/observability.md | 6 +-
docs/src/en/operation/system_table.md | 5 +-
docs/src/en/operation/table.md | 2 +-
docs/src/en/quick_start.md | 16 +-
docs/src/en/sdk/go.md | 26 +-
docs/src/en/sdk/java.md | 10 +-
docs/src/en/sdk/python.md | 10 +-
docs/src/en/sdk/rust.md | 22 +-
docs/src/en/sql/dml/insert.md | 2 +-
...-cluster0.toml => config-horaedb-cluster0.toml} | 0
...-cluster1.toml => config-horaedb-cluster1.toml} | 0
...luster0.toml => config-horaemeta-cluster0.toml} | 0
...luster1.toml => config-horaemeta-cluster1.toml} | 0
...luster2.toml => config-horaemeta-cluster2.toml} | 0
...alone.toml => config-horaemeta-standalone.toml} | 0
docs/src/resources/config_kafka_oss.toml | 6 +-
docs/src/resources/config_local_oss.toml | 8 +-
docs/src/resources/config_obkv_oss.toml | 6 +-
docs/src/resources/grafana-dashboard.json | 2 +-
54 files changed, 226 insertions(+), 1279 deletions(-)
diff --git a/README-CN.md b/README-CN.md
index 088c801..9d9fcef 100644
--- a/README-CN.md
+++ b/README-CN.md
@@ -1,12 +1,12 @@
## HoraeDB 文档
欢迎来到 HoraeDB 文档仓库!
-这个仓库存放的是[HoraeDB 文档网站](https://ceresdb.github.io/docs)的源文件，文档网站使用 mdbook 工具生成。
+这个仓库存放的是[HoraeDB
文档网站](https://apache.github.io/incubator-horaedb-docs/)的源文件，文档网站使用 mdbook 工具生成。
本仓库的所有文件均使用标准 markdown 语法编写。
## Contributing
欢迎大家加入到 HoraeDB 文档建设中，一起把文档做的更好更全。如果你遇到了 HoraeDB 的文档问题，可随时
-- 提 [issue](https://github.com/CeresDB/docs/issues) 来反馈，或者
-- 直接提交 [Pull Request](https://github.com/CeresDB/docs/pulls) 来进行修改。
+- 提 [issue](https://github.com/apache/incubator-horaedb-docs/issues) 来反馈，或者
+- 直接提交 [Pull Request](https://github.com/apache/incubator-horaedb-docs/pulls)
来进行修改。
diff --git a/README.md b/README.md
index dbffaa9..6264497 100644
--- a/README.md
+++ b/README.md
@@ -2,7 +2,7 @@
Welcome to HoraeDB documentation!
-This repository stores all the source files of [HoraeDB docs
website](https://ceresdb.github.io/docs), the website is generated with
[mdbook](https://rust-lang.github.io/mdBook/).
+This repository stores all the source files of [HoraeDB docs
website](https://apache.github.io/incubator-horaedb-docs/), the website is
generated with [mdbook](https://rust-lang.github.io/mdBook/).
**All files are written in standard markdown.**
@@ -12,5 +12,5 @@ We very much welcome any contributions from the community to
make HoraeDB docume
You can
-- Open an [issue](https://github.com/CeresDB/docs/issues) with any
suggestions, or
-- Submit a [pull request](https://github.com/CeresDB/docs/pulls) to fix errors.
+- Open an [issue](https://github.com/apache/incubator-horaedb-docs/issues)
with any suggestions, or
+- Submit a [pull
request](https://github.com/apache/incubator-horaedb-docs/pulls) to fix errors.
diff --git a/docs/book.toml b/docs/book.toml
index 79d85b3..dc9400f 100644
--- a/docs/book.toml
+++ b/docs/book.toml
@@ -20,8 +20,7 @@ title = "HoraeDB 文档"
command = "/bin/bash ../../move.sh"
[output.html]
-cname = "docs.ceresdb.io"
-git-repository-url = "https://github.com/CeresDB/horaedb";
+git-repository-url = "https://github.com/apache/incubator-horaedb";
edit-url-template = "https://github.com/CeresDB/docs/edit/main/docs/{path}";
additional-css = ["style.css"]
additional-js = ["sidebar.js"]
diff --git a/docs/src/cn/about.md b/docs/src/cn/about.md
index 2deefbd..f0c45c9 100644
--- a/docs/src/cn/about.md
+++ b/docs/src/cn/about.md
@@ -1,10 +1,8 @@
-[](https://github.com/CeresDB/horaedb/actions/workflows/ci.yml)
-[](https://github.com/CeresDB/horaedb/issues)
-[](https://join.slack.com/t/ceresdbcommunity/shared_invite/zt-1dcbv8yq8-Fv8aVUb6ODTL7kxbzs9fnA)
-[](https://hub.docker.com/r/ceresdb/ceresdb-server)
+[](https://github.com/apache/incubator-horaedb/actions/workflows/ci.yml)
+[](https://github.com/apache/incubator-horaedb/issues)
HoraeDB 是一款高性能、分布式的云原生时序数据库。
diff --git a/docs/src/cn/cluster_deployment/no_meta.md
b/docs/src/cn/cluster_deployment/no_meta.md
index 96475b5..bef35df 100644
--- a/docs/src/cn/cluster_deployment/no_meta.md
+++ b/docs/src/cn/cluster_deployment/no_meta.md
@@ -265,8 +265,8 @@ port = 18831
启动命令如下：
```shell
-sudo docker run -d -t --name horaedb_0 -p 5440:5440 -p 8831:8831 -v
$(pwd)/config_0.toml:/etc/ceresdb/ceresdb.toml ceresdb/ceresdb-server
-sudo docker run -d -t --name horaedb_1 -p 15440:15440 -p 18831:18831 -v
$(pwd)/config_1.toml:/etc/ceresdb/ceresdb.toml ceresdb/ceresdb-server
+sudo docker run -d -t --name horaedb_0 -p 5440:5440 -p 8831:8831 -v
$(pwd)/config_0.toml:/etc/horaedb/horaedb.toml horaedb/horaedb-server
+sudo docker run -d -t --name horaedb_1 -p 15440:15440 -p 18831:18831 -v
$(pwd)/config_1.toml:/etc/horaedb/horaedb.toml horaedb/horaedb-server
```
容器启动成功后，两个实例的 HoraeDB 集群就搭建完成了，可以开始提供读写服务。
diff --git a/docs/src/cn/cluster_deployment/with_meta.md
b/docs/src/cn/cluster_deployment/with_meta.md
index 57d0acb..d1abbf1 100644
--- a/docs/src/cn/cluster_deployment/with_meta.md
+++ b/docs/src/cn/cluster_deployment/with_meta.md
@@ -16,7 +16,7 @@ HoraeMeta 本身通过嵌入式的 [ETCD](https://github.com/etcd-io/etcd) 保
#### 启动配置
-目前 HoraeMeta 支持以配置文件和环境变量两种方式来指定服务启动配置。我们提供了配置文件方式启动的示例，具体可以参考
[config](https://github.com/CeresDB/horaemeta/tree/main/config)。
+目前 HoraeMeta 支持以配置文件和环境变量两种方式来指定服务启动配置。我们提供了配置文件方式启动的示例，具体可以参考
[config](https://github.com/apache/incubator-horaedb-meta/tree/main/config)。
环境变量的配置优先级高于配置文件，当同时存在时，以环境变量为准。
#### 动态拓扑和静态拓扑
@@ -36,29 +36,29 @@ HoraeMeta 基于 etcd 实现高可用，在线上环境我们一般部署多个
```bash
docker run -d --name horaemeta-server \
-p 2379:2379 \
- ceresdb/ceresmeta-server:latest
+ ghcr.io/apache/horaemeta-server:nightly-20231225-ab067bf0
```
- 多节点
```bash
-wget
https://raw.githubusercontent.com/CeresDB/docs/main/docs/src/resources/config-ceresmeta-cluster0.toml
+wget
https://raw.githubusercontent.com/apache/incubator-horaedb-docs/main/docs/src/resources/config-horaemeta-cluster0.toml
docker run -d --network=host --name horaemeta-server0 \
- -v $(pwd)/config-ceresmeta-cluster0.toml:/etc/ceresmeta/ceresmeta.toml \
- ceresdb/ceresmeta-server:latest
+ -v $(pwd)/config-horaemeta-cluster0.toml:/etc/horaemeta/horaemeta.toml \
+ ghcr.io/apache/horaemeta-server:nightly-20231225-ab067bf0
-wget
https://raw.githubusercontent.com/CeresDB/docs/main/docs/src/resources/config-ceresmeta-cluster1.toml
+wget
https://raw.githubusercontent.com/apache/incubator-horaedb-docs/main/docs/src/resources/config-horaemeta-cluster1.toml
docker run -d --network=host --name horaemeta-server1 \
- -v $(pwd)/config-ceresmeta-cluster1.toml:/etc/ceresmeta/ceresmeta.toml \
- ceresdb/ceresmeta-server:latest
+ -v $(pwd)/config-horaemeta-cluster1.toml:/etc/horaemeta/horaemeta.toml \
+ ghcr.io/apache/horaemeta-server:nightly-20231225-ab067bf0
-wget
https://raw.githubusercontent.com/CeresDB/docs/main/docs/src/resources/config-ceresmeta-cluster2.toml
+wget
https://raw.githubusercontent.com/apache/incubator-horaedb-docs/main/docs/src/resources/config-horaemeta-cluster2.toml
docker run -d --network=host --name horaemeta-server2 \
- -v $(pwd)/config-ceresmeta-cluster2.toml:/etc/ceresmeta/ceresmeta.toml \
- ceresdb/ceresmeta-server:latest
+ -v $(pwd)/config-horaemeta-cluster2.toml:/etc/horaemeta/horaemeta.toml \
+ ghcr.io/apache/horaemeta-server:nightly-20231225-ab067bf0
```
如果 HoraeDB 底层采用的是远程存储，可以环境变量来开启动态调度：只需将 `-e ENABLE_SCHEDULE=true` 加入到 docker
run 命令中去。
@@ -76,7 +76,7 @@ docker run -d --network=host --name horaemeta-server2 \
注意：在生产环境中如果我们把 HoraeDB 部署在多个节点上时，请按照如下方式把机器的网络地址设置到环境变量中：
```shell
-export CERESDB_SERVER_ADDR="{server_addr}:8831"
+export HORAEDB_SERVER_ADDR="{server_addr}:8831"
```
注意，此网络地址用于 HoraeMeta 和 HoraeDB 通信使用，需保证网络联通可用。
@@ -90,7 +90,7 @@ export CERESDB_SERVER_ADDR="{server_addr}:8831"
```toml
[analytic.storage.object_store]
type = "Local"
-data_dir = "/home/admin/data/ceresdb"
+data_dir = "/home/admin/data/horaedb"
```
#### OSS
@@ -131,7 +131,7 @@ prefix = "{prefix}"
```toml
[analytic.wal]
type = "RocksDB"
-data_dir = "/home/admin/data/ceresdb"
+data_dir = "/home/admin/data/horaedb"
```
#### OceanBase
@@ -227,7 +227,7 @@ store_timeout = "5s"
[analytic.wal]
type = "RocksDB"
-data_dir = "/home/admin/data/ceresdb"
+data_dir = "/home/admin/data/horaedb"
[analytic.storage]
mem_cache_capacity = "20GB"
@@ -236,7 +236,7 @@ mem_cache_partition_bits = 8
[analytic.storage.object_store]
type = "Local"
-data_dir = "/home/admin/data/ceresdb/"
+data_dir = "/home/admin/data/horaedb/"
[analytic.table_opts]
arena_block_size = 2097152
@@ -262,27 +262,8 @@ memory_limit = "4G"
```bash
docker run -d --name horaemeta-server \
-p 2379:2379 \
- ceresdb/ceresmeta-server
+ ghcr.io/apache/horaemeta-server:nightly-20231225-ab067bf0
```
HoraeMeta 启动好了，没有问题之后，就可以把 HoraeDB 的容器创建出来：
-
-```bash
-wget
https://raw.githubusercontent.com/CeresDB/docs/main/docs/src/resources/config-ceresdb-cluster0.toml
-
-docker run -d --name horaedb-server0 \
- -p 5440:5440 \
- -p 8831:8831 \
- -p 3307:3307 \
- -v $(pwd)/config-ceresdb-cluster0.toml:/etc/ceresdb/ceresdb.toml \
- ceresdb/ceresdb-server
-
-wget
https://raw.githubusercontent.com/CeresDB/docs/main/docs/src/resources/config-ceresdb-cluster1.toml
-
-docker run -d --name horaedb-server1 \
- -p 5441:5441 \
- -p 8832:8832 \
- -p 13307:13307 \
- -v $(pwd)/config-ceresdb-cluster1.toml:/etc/ceresdb/ceresdb.toml \
- ceresdb/ceresdb-server
-```
+TODO: 补充完整
diff --git a/docs/src/cn/design/architecture.md
b/docs/src/cn/design/architecture.md
index 99cb814..0c6dd1f 100644
--- a/docs/src/cn/design/architecture.md
+++ b/docs/src/cn/design/architecture.md
@@ -58,7 +58,7 @@ HoraeDB 是一个时序数据库，与经典时序数据库相比，HoraeDB 的
### RPC 层
-模块路径：https://github.com/CeresDB/horaedb/tree/main/server
+模块路径：https://github.com/apache/incubator-horaedb/tree/main/server
当前的 RPC 支持多种协议，包括 HTTP、gRPC、MySQL。
@@ -66,7 +66,7 @@ HoraeDB 是一个时序数据库，与经典时序数据库相比，HoraeDB 的
### SQL 层
-模块路径：https://github.com/CeresDB/horaedb/tree/main/query_frontend
+模块路径：https://github.com/apache/incubator-horaedb/tree/main/query_frontend
SQL 层负责解析 SQL 并生成查询计划。
@@ -74,13 +74,13 @@ HoraeDB 基于
[sqlparser](https://github.com/sqlparser-rs/sqlparser-rs) 提供
### Interpreter
-模块路径：https://github.com/CeresDB/horaedb/tree/main/interpreters
+模块路径：https://github.com/apache/incubator-horaedb/tree/main/interpreters
`Interpreter` 模块封装了 SQL 的 `CRUD` 操作。在查询流程中，一个 SQL
语句会经过解析，生成出对应的查询计划，然后便会在特定的解释器中执行，例如 `SelectInterpreter`、`InsertInterpreter` 等。
### Catalog
-模块路径：https://github.com/CeresDB/horaedb/tree/main/catalog_impls
+模块路径：https://github.com/apache/incubator-horaedb/tree/main/catalog_impls
`Catalog` 实际上是管理元数据的模块，HoraeDB 采用的元数据分级与 PostgreSQL 类似：`Catalog > Schema >
Table`，但目前它们只用作命名空间。
@@ -88,7 +88,7 @@ HoraeDB 基于
[sqlparser](https://github.com/sqlparser-rs/sqlparser-rs) 提供
### 查询引擎
-模块路径：https://github.com/CeresDB/horaedb/tree/main/query_engine
+模块路径：https://github.com/apache/incubator-horaedb/tree/main/query_engine
查询引擎负责优化和执行由 SQL 层解析出来的 SQL 计划，目前查询引擎实际上基于
[DataFusion](https://github.com/apache/arrow-datafusion) 来实现的。
@@ -96,7 +96,7 @@ HoraeDB 基于
[sqlparser](https://github.com/sqlparser-rs/sqlparser-rs) 提供
### Pluggable Table Engine
-模块路径：https://github.com/CeresDB/horaedb/tree/main/table_engine
+模块路径：https://github.com/apache/incubator-horaedb/tree/main/table_engine
`Table Engine` 是 HoraeDB 中用于管理表的存储引擎，其可插拔性是 HoraeDB 的一个核心设计，对于实现我们的一些长远目标（比如增加
Log 或 Tracing 类型数据的存储引擎）至关重要。HoraeDB 将会有多种 `Table Engine`
用于不同的工作负载，根据工作负载模式，应该选择最合适的存储引擎。
@@ -117,7 +117,7 @@ HoraeDB 基于
[sqlparser](https://github.com/sqlparser-rs/sqlparser-rs) 提供
#### WAL
-模块路径：https://github.com/CeresDB/horaedb/tree/main/wal
+模块路径：https://github.com/apache/incubator-horaedb/tree/main/wal
HoraeDB 处理数据的模型是 `WAL` + `MemTable`，最近写入的数据首先被写入 `WAL`，然后写入 `MemTable`，在
`MemTable` 中累积了一定数量的数据后，该数据将以便于查询的形式被重新构建，并存储到持久化设备上。
@@ -129,15 +129,15 @@ HoraeDB 处理数据的模型是 `WAL` + `MemTable`，最近写入的数据首
#### MemTable
-模块路径：https://github.com/CeresDB/horaedb/tree/main/analytic_engine/src/memtable
+模块路径：https://github.com/apache/incubator-horaedb/tree/main/analytic_engine/src/memtable
由于 `WAL` 无法提供高效的查询，因此新写入的数据会存储一份到 `Memtable` 用于查询，并且在积累了一定数量后，HoraeDB 将
`MemTable` 中的数据组织成便于查询的存储格式（`SST`）并存储到持久化设备中。
-MemTable 的当前实现基于 [agatedb 的
skiplist](https://github.com/tikv/agatedb/blob/8510bff2bfde5b766c3f83cf81c00141967d48a4/skiplist)。它允许并发读取和写入，并且可以根据
[Arena](https://github.com/CeresDB/horaedb/tree/main/components/skiplist)
控制内存使用。
+MemTable 的当前实现基于 [agatedb 的
skiplist](https://github.com/tikv/agatedb/blob/8510bff2bfde5b766c3f83cf81c00141967d48a4/skiplist)。它允许并发读取和写入，并且可以根据
[Arena](https://github.com/apache/incubator-horaedb/tree/main/components/skiplist)
控制内存使用。
#### Flush
-模块路径：https://github.com/CeresDB/horaedb/blob/main/analytic_engine/src/instance/flush_compaction.rs
+模块路径：https://github.com/apache/incubator-horaedb/blob/main/analytic_engine/src/instance/flush_compaction.rs
当 `MemTable` 的内存使用量达到阈值时，`Flush` 操作会选择一些老的 `MemTable`，将其中的数据组织成便于查询的 `SST`
存储到持久化设备上。
@@ -145,13 +145,13 @@ MemTable 的当前实现基于 [agatedb 的
skiplist](https://github.com/tikv/ag
#### Compaction
-模块路径：https://github.com/CeresDB/horaedb/tree/main/analytic_engine/src/compaction
+模块路径：https://github.com/apache/incubator-horaedb/tree/main/analytic_engine/src/compaction
`MemTable` 的数据被刷新为 `SST` 文件，但最近刷新的 `SST` 文件可能非常小，而过小或过多的 `SST`
文件会导致查询性能不佳，因此，引入 `Compaction` 来重新整理 SST 文件，使多个较小的 `SST` 文件可以合并成较大的 `SST` 文件。
#### Manifest
-模块路径：https://github.com/CeresDB/horaedb/tree/main/analytic_engine/src/meta
+模块路径：https://github.com/apache/incubator-horaedb/tree/main/analytic_engine/src/meta
`Manifest` 负责管理每个表的元数据，包括：
@@ -163,7 +163,7 @@ MemTable 的当前实现基于 [agatedb 的
skiplist](https://github.com/tikv/ag
#### Object Storage
-模块路径：https://github.com/CeresDB/horaedb/tree/main/components/object_store
+模块路径：https://github.com/apache/incubator-horaedb/tree/main/components/object_store
`Flush` 操作产生的 `SST` 文件需要持久化存储，而用于抽象持久化存储设备的就是 `Object Storage`，其中包括多种实现：
@@ -174,7 +174,7 @@ HoraeDB 的分布式架构的一个核心特性就是存储和计算分离，因
#### SST
-模块路径：https://github.com/CeresDB/horaedb/tree/main/analytic_engine/src/sst
+模块路径：https://github.com/apache/incubator-horaedb/tree/main/analytic_engine/src/sst
`SST` 本身实际上是一种抽象，可以有多种具体实现。目前的实现是基于
[Parquet](https://parquet.apache.org/)，它是一种面向列的数据文件格式，旨在实现高效的数据存储和检索。
@@ -182,7 +182,7 @@ HoraeDB 的分布式架构的一个核心特性就是存储和计算分离，因
#### Space
-模块路径：https://github.com/CeresDB/horaedb/blob/main/analytic_engine/src/space.rs
+模块路径：https://github.com/apache/incubator-horaedb/blob/main/analytic_engine/src/space.rs
在 `Analytic Engine` 中，有一个叫做 `space` 的概念，这里着重解释一下，以解决阅读源代码时出现的一些歧义。
实际上，`Analytic Engine` 没有 `catalog` 和 `schema` 的概念，只提供两个层级的关系：`space` 和
`table`。在实现中，上层的 `schema id`（要求在所有的 `catalogs` 中都应该是唯一的）实际上会直接映射成 `space id`。
@@ -251,7 +251,7 @@ HoraeDB 的分布式架构的一个核心特性就是存储和计算分离，因
- `SelectInterpreter` 获取结果并将其传输给 Protocol 模块；
- 协议模块完成转换结果后，Server 模块将其响应给客户端。
-以下是[v1.2.2](https://github.com/CeresDB/horaedb/releases/tag/v1.2.2)的函数调用流程:
+以下是[v1.2.2](https://github.com/apache/incubator-horaedb/releases/tag/v1.2.2)的函数调用流程:
```
┌───────────────────────◀─────────────┐ ┌───────────────────────┐
diff --git a/docs/src/cn/design/table_partitioning.md
b/docs/src/cn/design/table_partitioning.md
index 08c3ae2..8e429c7 100644
--- a/docs/src/cn/design/table_partitioning.md
+++ b/docs/src/cn/design/table_partitioning.md
@@ -69,9 +69,9 @@ CREATE TABLE `demo`(
由于分区表数据实际上是存放在不同的物理表中，所以查询时需要根据查询请求计算出实际请求的物理表。
-首先查询会根据查询语句计算出要查询的物理表， 然后通过 HoraeDB 内部服务 [remote
engine](https://github.com/CeresDB/horaedb/blob/89dca646c627de3cee2133e8f3df96d89854c1a3/server/src/grpc/remote_engine_service/mod.rs)
远程请求物理表所在节点获取数据（支持谓词下推）。
+首先查询会根据查询语句计算出要查询的物理表， 然后通过 HoraeDB 内部服务 [remote
engine](https://github.com/apache/incubator-horaedb/blob/89dca646c627de3cee2133e8f3df96d89854c1a3/server/src/grpc/remote_engine_service/mod.rs)
远程请求物理表所在节点获取数据（支持谓词下推）。
-分区表的实现在
[PartitionTableImpl](https://github.com/CeresDB/horaedb/blob/89dca646c627de3cee2133e8f3df96d89854c1a3/analytic_engine/src/table/partition.rs)
中。
+分区表的实现在
[PartitionTableImpl](https://github.com/apache/incubator-horaedb/blob/89dca646c627de3cee2133e8f3df96d89854c1a3/analytic_engine/src/table/partition.rs)
中。
- 第一步：解析查询 sql，根据查询参数计算出要查询的物理表。
- 第二步：查询物理表数据。
@@ -105,7 +105,7 @@ CREATE TABLE `demo`(
- 带有 `and`, `or`, `in`, `=` 的过滤器将选择特定的子表。
- 支持模糊匹配过滤器，如 `<`, `>`，但可能性能较差，因为它会扫描所有物理表。
-`Key partitioning` 规则实现在
[KeyRule](https://github.com/CeresDB/horaedb/blob/89dca646c627de3cee2133e8f3df96d89854c1a3/table_engine/src/partition/rule/key.rs)。
+`Key partitioning` 规则实现在
[KeyRule](https://github.com/apache/incubator-horaedb/blob/89dca646c627de3cee2133e8f3df96d89854c1a3/table_engine/src/partition/rule/key.rs)。
## 写入
diff --git a/docs/src/cn/dev/compile_run.md b/docs/src/cn/dev/compile_run.md
index 87a64d8..fb06f82 100644
--- a/docs/src/cn/dev/compile_run.md
+++ b/docs/src/cn/dev/compile_run.md
@@ -56,5 +56,5 @@ cargo build --release
然后可以使用特定的配置文件运行 HoraeDB。
```bash
-./target/release/ceresdb-server --config ./docs/minimal.toml
+./target/release/horaedb-server --config ./docs/minimal.toml
```
diff --git a/docs/src/cn/dev/crate-deps.dot b/docs/src/cn/dev/crate-deps.dot
deleted file mode 100644
index 397816c..0000000
--- a/docs/src/cn/dev/crate-deps.dot
+++ /dev/null
@@ -1,89 +0,0 @@
-// Licensed to the Apache Software Foundation (ASF) under one
-// or more contributor license agreements. See the NOTICE file
-// distributed with this work for additional information
-// regarding copyright ownership. The ASF licenses this file
-// to you under the Apache License, Version 2.0 (the
-// "License"); you may not use this file except in compliance
-// with the License. You may obtain a copy of the License at
-//
-// http://www.apache.org/licenses/LICENSE-2.0
-//
-// Unless required by applicable law or agreed to in writing,
-// software distributed under the License is distributed on an
-// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-// KIND, either express or implied. See the License for the
-// specific language governing permissions and limitations
-// under the License.
-
-// to update svg, run:
-// ```bash
-// dot -Tsvg crate-deps.dot > ./crate-deps.svg
-// ```
-
-digraph G {
-
- arrow_deps
-
- analytic_engine -> arrow_deps
- analytic_engine -> proto
- analytic_engine -> table_engine
- analytic_engine -> wal
-
- catalog -> table_engine
-
- catalog_impls -> catalog
- catalog_impls -> system_catalog
- catalog_impls -> table_engine
- catalog_impls -> cluster
- catalog_impls -> meta_client
-
- cluster -> analytic_engine
- cluster -> catalog
- cluster -> meta_client
-
- interpreters -> catalog
- interpreters -> sql
- interpreters -> table_engine
- interpreters -> df_operator
- interpreters -> query_engine
- interpreters -> arrow_deps
-
- query_engine -> arrow_deps
- query_engine -> sql
- query_engine -> table_engine
- query_engine -> df_operator
-
- server -> analytic_engine
- server -> arrow_deps
- server -> catalog
- server -> interpreters
- server -> meta_client
- server -> query_engine
- server -> sql
- server -> system_catalog
- server -> table_engine
- server -> df_operator
-
- sql -> arrow_deps
- sql -> catalog
- sql -> table_engine
- sql -> df_operator
-
- system_catalog -> arrow_deps
- system_catalog -> catalog
- system_catalog -> proto
- system_catalog -> table_engine
-
- table_engine -> arrow_deps
- table_engine -> proto
-
- df_operator -> arrow_deps
-
- ceresdb -> analytic_engine
- ceresdb -> catalog
- ceresdb -> catalog_impls
- ceresdb -> query_engine
- ceresdb -> server
- ceresdb -> table_engine
- ceresdb -> df_operator
-}
diff --git a/docs/src/cn/dev/crate-deps.svg b/docs/src/cn/dev/crate-deps.svg
deleted file mode 100644
index 6e87508..0000000
--- a/docs/src/cn/dev/crate-deps.svg
+++ /dev/null
@@ -1,415 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN"
- "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
-<!-- Generated by graphviz version 3.0.0 (0)
- -->
-<!-- Title: G Pages: 1 -->
-<svg width="1092pt" height="548pt"
- viewBox="0.00 0.00 1092.29 548.00" xmlns="http://www.w3.org/2000/svg";
xmlns:xlink="http://www.w3.org/1999/xlink";>
-<g id="graph0" class="graph" transform="scale(1 1) rotate(0) translate(4 544)">
-<title>G</title>
-<polygon fill="white" stroke="transparent" points="-4,4 -4,-544 1088.29,-544
1088.29,4 -4,4"/>
-<!-- arrow_deps -->
-<g id="node1" class="node">
-<title>arrow_deps</title>
-<ellipse fill="none" stroke="black" cx="758.29" cy="-18" rx="51.99" ry="18"/>
-<text text-anchor="middle" x="758.29" y="-14.3" font-family="Times,serif"
font-size="14.00">arrow_deps</text>
-</g>
-<!-- analytic_engine -->
-<g id="node2" class="node">
-<title>analytic_engine</title>
-<ellipse fill="none" stroke="black" cx="66.29" cy="-162" rx="66.09" ry="18"/>
-<text text-anchor="middle" x="66.29" y="-158.3" font-family="Times,serif"
font-size="14.00">analytic_engine</text>
-</g>
-<!-- analytic_engine->arrow_deps -->
-<g id="edge1" class="edge">
-<title>analytic_engine->arrow_deps</title>
-<path fill="none" stroke="black" d="M104.49,-147.15C159.77,-127.62
265.59,-92.13 358.29,-72 477.37,-46.15 619.29,-30.96 698.05,-23.88"/>
-<polygon fill="black" stroke="black" points="698.61,-27.34 708.27,-22.97
698,-20.37 698.61,-27.34"/>
-</g>
-<!-- proto -->
-<g id="node3" class="node">
-<title>proto</title>
-<ellipse fill="none" stroke="black" cx="282.29" cy="-18" rx="29.5" ry="18"/>
-<text text-anchor="middle" x="282.29" y="-14.3" font-family="Times,serif"
font-size="14.00">proto</text>
-</g>
-<!-- analytic_engine->proto -->
-<g id="edge2" class="edge">
-<title>analytic_engine->proto</title>
-<path fill="none" stroke="black" d="M65.02,-143.86C64.52,-123.95 66.92,-91.37
85.29,-72 126.14,-28.95 197.92,-19.55 242.63,-18.19"/>
-<polygon fill="black" stroke="black" points="242.9,-21.69 252.84,-18.01
242.78,-14.69 242.9,-21.69"/>
-</g>
-<!-- table_engine -->
-<g id="node4" class="node">
-<title>table_engine</title>
-<ellipse fill="none" stroke="black" cx="606.29" cy="-90" rx="55.79" ry="18"/>
-<text text-anchor="middle" x="606.29" y="-86.3" font-family="Times,serif"
font-size="14.00">table_engine</text>
-</g>
-<!-- analytic_engine->table_engine -->
-<g id="edge3" class="edge">
-<title>analytic_engine->table_engine</title>
-<path fill="none" stroke="black" d="M113.75,-149.42C122.86,-147.43
132.34,-145.52 141.29,-144 283.8,-119.8 452.79,-103.64 542.65,-96.03"/>
-<polygon fill="black" stroke="black" points="543,-99.52 552.68,-95.19
542.42,-92.54 543,-99.52"/>
-</g>
-<!-- wal -->
-<g id="node5" class="node">
-<title>wal</title>
-<ellipse fill="none" stroke="black" cx="121.29" cy="-90" rx="27" ry="18"/>
-<text text-anchor="middle" x="121.29" y="-86.3" font-family="Times,serif"
font-size="14.00">wal</text>
-</g>
-<!-- analytic_engine->wal -->
-<g id="edge4" class="edge">
-<title>analytic_engine->wal</title>
-<path fill="none" stroke="black" d="M79.61,-144.05C86.59,-135.17 95.26,-124.14
102.87,-114.45"/>
-<polygon fill="black" stroke="black" points="105.8,-116.38 109.23,-106.36
100.3,-112.06 105.8,-116.38"/>
-</g>
-<!-- table_engine->arrow_deps -->
-<g id="edge42" class="edge">
-<title>table_engine->arrow_deps</title>
-<path fill="none" stroke="black" d="M637.05,-74.83C660.67,-63.96 693.45,-48.86
718.97,-37.11"/>
-<polygon fill="black" stroke="black" points="720.74,-40.15 728.36,-32.79
717.81,-33.79 720.74,-40.15"/>
-</g>
-<!-- table_engine->proto -->
-<g id="edge43" class="edge">
-<title>table_engine->proto</title>
-<path fill="none" stroke="black" d="M561.24,-79.27C496.78,-65.34 379.41,-39.98
319.56,-27.05"/>
-<polygon fill="black" stroke="black" points="319.94,-23.55 309.42,-24.86
318.46,-30.39 319.94,-23.55"/>
-</g>
-<!-- catalog -->
-<g id="node6" class="node">
-<title>catalog</title>
-<ellipse fill="none" stroke="black" cx="511.29" cy="-162" rx="36.29" ry="18"/>
-<text text-anchor="middle" x="511.29" y="-158.3" font-family="Times,serif"
font-size="14.00">catalog</text>
-</g>
-<!-- catalog->table_engine -->
-<g id="edge5" class="edge">
-<title>catalog->table_engine</title>
-<path fill="none" stroke="black" d="M530.98,-146.5C544.15,-136.79
561.74,-123.83 576.6,-112.88"/>
-<polygon fill="black" stroke="black" points="579.01,-115.45 584.98,-106.7
574.86,-109.82 579.01,-115.45"/>
-</g>
-<!-- catalog_impls -->
-<g id="node7" class="node">
-<title>catalog_impls</title>
-<ellipse fill="none" stroke="black" cx="238.29" cy="-306" rx="59.59" ry="18"/>
-<text text-anchor="middle" x="238.29" y="-302.3" font-family="Times,serif"
font-size="14.00">catalog_impls</text>
-</g>
-<!-- catalog_impls->table_engine -->
-<g id="edge8" class="edge">
-<title>catalog_impls->table_engine</title>
-<path fill="none" stroke="black" d="M244,-287.79C251.14,-268.41 264.94,-236.91
285.29,-216 355.98,-143.41 473.7,-112.15 545.23,-99.31"/>
-<polygon fill="black" stroke="black" points="546.18,-102.7 555.44,-97.55
544.99,-95.8 546.18,-102.7"/>
-</g>
-<!-- catalog_impls->catalog -->
-<g id="edge6" class="edge">
-<title>catalog_impls->catalog</title>
-<path fill="none" stroke="black" d="M293.66,-299.08C335.23,-292.6
392.18,-279.24 435.29,-252 461.03,-235.74 482.68,-208.03 496.2,-187.84"/>
-<polygon fill="black" stroke="black" points="499.15,-189.72 501.66,-179.43
493.28,-185.91 499.15,-189.72"/>
-</g>
-<!-- system_catalog -->
-<g id="node8" class="node">
-<title>system_catalog</title>
-<ellipse fill="none" stroke="black" cx="360.29" cy="-234" rx="65.79" ry="18"/>
-<text text-anchor="middle" x="360.29" y="-230.3" font-family="Times,serif"
font-size="14.00">system_catalog</text>
-</g>
-<!-- catalog_impls->system_catalog -->
-<g id="edge7" class="edge">
-<title>catalog_impls->system_catalog</title>
-<path fill="none" stroke="black" d="M264.77,-289.81C282.19,-279.81
305.22,-266.6 324.3,-255.65"/>
-<polygon fill="black" stroke="black" points="326.1,-258.66 333.03,-250.64
322.61,-252.58 326.1,-258.66"/>
-</g>
-<!-- cluster -->
-<g id="node9" class="node">
-<title>cluster</title>
-<ellipse fill="none" stroke="black" cx="166.29" cy="-234" rx="34.39" ry="18"/>
-<text text-anchor="middle" x="166.29" y="-230.3" font-family="Times,serif"
font-size="14.00">cluster</text>
-</g>
-<!-- catalog_impls->cluster -->
-<g id="edge9" class="edge">
-<title>catalog_impls->cluster</title>
-<path fill="none" stroke="black" d="M221.23,-288.41C211.73,-279.17
199.76,-267.54 189.43,-257.49"/>
-<polygon fill="black" stroke="black" points="191.86,-254.97 182.25,-250.51
186.98,-259.99 191.86,-254.97"/>
-</g>
-<!-- meta_client -->
-<g id="node10" class="node">
-<title>meta_client</title>
-<ellipse fill="none" stroke="black" cx="202.29" cy="-162" rx="51.99" ry="18"/>
-<text text-anchor="middle" x="202.29" y="-158.3" font-family="Times,serif"
font-size="14.00">meta_client</text>
-</g>
-<!-- catalog_impls->meta_client -->
-<g id="edge10" class="edge">
-<title>catalog_impls->meta_client</title>
-<path fill="none" stroke="black" d="M233.95,-287.87C227.79,-263.56
216.45,-218.82 209.14,-190.01"/>
-<polygon fill="black" stroke="black" points="212.5,-189.02 206.65,-180.19
205.72,-190.74 212.5,-189.02"/>
-</g>
-<!-- system_catalog->arrow_deps -->
-<g id="edge38" class="edge">
-<title>system_catalog->arrow_deps</title>
-<path fill="none" stroke="black" d="M367.26,-215.81C375.79,-196.46
391.8,-164.97 413.29,-144 492.45,-66.78 622.88,-36.81 698.66,-25.51"/>
-<polygon fill="black" stroke="black" points="699.57,-28.92 708.98,-24.04
698.58,-21.99 699.57,-28.92"/>
-</g>
-<!-- system_catalog->proto -->
-<g id="edge40" class="edge">
-<title>system_catalog->proto</title>
-<path fill="none" stroke="black" d="M354.04,-215.85C340.43,-178.49
308.01,-89.56 291.83,-45.16"/>
-<polygon fill="black" stroke="black" points="295.07,-43.84 288.36,-35.64
288.5,-46.23 295.07,-43.84"/>
-</g>
-<!-- system_catalog->table_engine -->
-<g id="edge41" class="edge">
-<title>system_catalog->table_engine</title>
-<path fill="none" stroke="black" d="M376.56,-216.26C396.29,-196.74
431.26,-164.54 466.29,-144 494.25,-127.61 528.19,-114.62 555.64,-105.59"/>
-<polygon fill="black" stroke="black" points="556.99,-108.84 565.44,-102.45
554.85,-102.17 556.99,-108.84"/>
-</g>
-<!-- system_catalog->catalog -->
-<g id="edge39" class="edge">
-<title>system_catalog->catalog</title>
-<path fill="none" stroke="black" d="M392.32,-218.15C416.88,-206.77
450.76,-191.06 476.09,-179.32"/>
-<polygon fill="black" stroke="black" points="477.74,-182.41 485.34,-175.03
474.79,-176.06 477.74,-182.41"/>
-</g>
-<!-- cluster->analytic_engine -->
-<g id="edge11" class="edge">
-<title>cluster->analytic_engine</title>
-<path fill="none" stroke="black" d="M146.54,-219.17C132.61,-209.42
113.67,-196.16 97.68,-184.97"/>
-<polygon fill="black" stroke="black" points="99.36,-181.87 89.16,-179.01
95.34,-187.61 99.36,-181.87"/>
-</g>
-<!-- cluster->catalog -->
-<g id="edge12" class="edge">
-<title>cluster->catalog</title>
-<path fill="none" stroke="black" d="M197.83,-226.6C259.9,-214.01
397.99,-185.99 468.33,-171.72"/>
-<polygon fill="black" stroke="black" points="469.09,-175.13 478.2,-169.71
467.7,-168.27 469.09,-175.13"/>
-</g>
-<!-- cluster->meta_client -->
-<g id="edge13" class="edge">
-<title>cluster->meta_client</title>
-<path fill="none" stroke="black" d="M174.83,-216.41C179.02,-208.25
184.18,-198.22 188.89,-189.07"/>
-<polygon fill="black" stroke="black" points="192.11,-190.45 193.57,-179.96
185.89,-187.25 192.11,-190.45"/>
-</g>
-<!-- interpreters -->
-<g id="node11" class="node">
-<title>interpreters</title>
-<ellipse fill="none" stroke="black" cx="760.29" cy="-378" rx="51.19" ry="18"/>
-<text text-anchor="middle" x="760.29" y="-374.3" font-family="Times,serif"
font-size="14.00">interpreters</text>
-</g>
-<!-- interpreters->arrow_deps -->
-<g id="edge19" class="edge">
-<title>interpreters->arrow_deps</title>
-<path fill="none" stroke="black" d="M760.2,-359.73C759.88,-302.19
758.84,-116.66 758.45,-46.35"/>
-<polygon fill="black" stroke="black" points="761.95,-46.07 758.39,-36.09
754.95,-46.11 761.95,-46.07"/>
-</g>
-<!-- interpreters->table_engine -->
-<g id="edge16" class="edge">
-<title>interpreters->table_engine</title>
-<path fill="none" stroke="black" d="M745.76,-360.63C725.94,-337.67
690.29,-293.99 667.29,-252 642.81,-207.29 623.88,-150.7 613.96,-117.9"/>
-<polygon fill="black" stroke="black" points="617.27,-116.72 611.07,-108.13
610.56,-118.71 617.27,-116.72"/>
-</g>
-<!-- interpreters->catalog -->
-<g id="edge14" class="edge">
-<title>interpreters->catalog</title>
-<path fill="none" stroke="black" d="M719.82,-366.76C692.55,-358.43
656.85,-344.64 630.29,-324 604.72,-304.12 553.3,-227.83 527.23,-187.82"/>
-<polygon fill="black" stroke="black" points="530.15,-185.89 521.77,-179.41
524.27,-189.7 530.15,-185.89"/>
-</g>
-<!-- sql -->
-<g id="node12" class="node">
-<title>sql</title>
-<ellipse fill="none" stroke="black" cx="703.29" cy="-234" rx="27" ry="18"/>
-<text text-anchor="middle" x="703.29" y="-230.3" font-family="Times,serif"
font-size="14.00">sql</text>
-</g>
-<!-- interpreters->sql -->
-<g id="edge15" class="edge">
-<title>interpreters->sql</title>
-<path fill="none" stroke="black" d="M753.53,-360.15C743.72,-335.71
725.44,-290.17 713.85,-261.29"/>
-<polygon fill="black" stroke="black" points="717.02,-259.8 710.05,-251.82
710.52,-262.41 717.02,-259.8"/>
-</g>
-<!-- df_operator -->
-<g id="node13" class="node">
-<title>df_operator</title>
-<ellipse fill="none" stroke="black" cx="927.29" cy="-162" rx="51.99" ry="18"/>
-<text text-anchor="middle" x="927.29" y="-158.3" font-family="Times,serif"
font-size="14.00">df_operator</text>
-</g>
-<!-- interpreters->df_operator -->
-<g id="edge17" class="edge">
-<title>interpreters->df_operator</title>
-<path fill="none" stroke="black" d="M810.06,-373.51C844.68,-368.26
888.84,-355.37 913.29,-324 943.3,-285.49 938.99,-224.95 933.14,-190.12"/>
-<polygon fill="black" stroke="black" points="936.57,-189.39 931.32,-180.19
929.68,-190.66 936.57,-189.39"/>
-</g>
-<!-- query_engine -->
-<g id="node14" class="node">
-<title>query_engine</title>
-<ellipse fill="none" stroke="black" cx="845.29" cy="-306" rx="59.29" ry="18"/>
-<text text-anchor="middle" x="845.29" y="-302.3" font-family="Times,serif"
font-size="14.00">query_engine</text>
-</g>
-<!-- interpreters->query_engine -->
-<g id="edge18" class="edge">
-<title>interpreters->query_engine</title>
-<path fill="none" stroke="black" d="M779.58,-361.12C790.91,-351.78
805.42,-339.84 817.92,-329.55"/>
-<polygon fill="black" stroke="black" points="820.29,-332.12 825.79,-323.06
815.84,-326.72 820.29,-332.12"/>
-</g>
-<!-- sql->arrow_deps -->
-<g id="edge34" class="edge">
-<title>sql->arrow_deps</title>
-<path fill="none" stroke="black" d="M707.61,-216.21C717.1,-179.26
739.87,-90.67 751.38,-45.89"/>
-<polygon fill="black" stroke="black" points="754.82,-46.57 753.92,-36.01
748.04,-44.82 754.82,-46.57"/>
-</g>
-<!-- sql->table_engine -->
-<g id="edge36" class="edge">
-<title>sql->table_engine</title>
-<path fill="none" stroke="black" d="M696.73,-216.4C688.99,-197.85
675.04,-167.36 658.29,-144 650.78,-133.52 641.21,-123.14 632.32,-114.39"/>
-<polygon fill="black" stroke="black" points="634.72,-111.84 625.08,-107.44
629.88,-116.89 634.72,-111.84"/>
-</g>
-<!-- sql->catalog -->
-<g id="edge35" class="edge">
-<title>sql->catalog</title>
-<path fill="none" stroke="black" d="M680.13,-224.56C647.68,-212.72
588.27,-191.06 549.29,-176.85"/>
-<polygon fill="black" stroke="black" points="550.44,-173.55 539.84,-173.41
548.04,-180.12 550.44,-173.55"/>
-</g>
-<!-- sql->df_operator -->
-<g id="edge37" class="edge">
-<title>sql->df_operator</title>
-<path fill="none" stroke="black" d="M727.27,-225.51C763.72,-214.12
833.8,-192.22 880.56,-177.6"/>
-<polygon fill="black" stroke="black" points="881.66,-180.93 890.16,-174.6
879.57,-174.25 881.66,-180.93"/>
-</g>
-<!-- df_operator->arrow_deps -->
-<g id="edge44" class="edge">
-<title>df_operator->arrow_deps</title>
-<path fill="none" stroke="black" d="M916.49,-144.29C903.47,-125.1 880.1,-93.48
854.29,-72 837.6,-58.1 816.71,-46.06 798.69,-36.99"/>
-<polygon fill="black" stroke="black" points="800.08,-33.77 789.56,-32.52
797,-40.06 800.08,-33.77"/>
-</g>
-<!-- query_engine->arrow_deps -->
-<g id="edge20" class="edge">
-<title>query_engine->arrow_deps</title>
-<path fill="none" stroke="black" d="M846.21,-287.85C847.64,-247.76
847.07,-145.77 810.29,-72 804.59,-60.55 795.49,-50.02 786.49,-41.41"/>
-<polygon fill="black" stroke="black" points="788.8,-38.77 779.03,-34.65
784.1,-43.96 788.8,-38.77"/>
-</g>
-<!-- query_engine->table_engine -->
-<g id="edge22" class="edge">
-<title>query_engine->table_engine</title>
-<path fill="none" stroke="black" d="M830.54,-288.49C803.07,-258.18
741.58,-192.36 683.29,-144 669.54,-132.59 653.37,-121.18 639.4,-111.9"/>
-<polygon fill="black" stroke="black" points="641.32,-108.96 631.04,-106.4
637.47,-114.82 641.32,-108.96"/>
-</g>
-<!-- query_engine->sql -->
-<g id="edge21" class="edge">
-<title>query_engine->sql</title>
-<path fill="none" stroke="black" d="M815.53,-290.33C791.4,-278.43
757.56,-261.75 733.36,-249.82"/>
-<polygon fill="black" stroke="black" points="734.79,-246.63 724.28,-245.34
731.7,-252.9 734.79,-246.63"/>
-</g>
-<!-- query_engine->df_operator -->
-<g id="edge23" class="edge">
-<title>query_engine->df_operator</title>
-<path fill="none" stroke="black" d="M855.02,-288.15C869.26,-263.49
895.9,-217.37 912.55,-188.53"/>
-<polygon fill="black" stroke="black" points="915.61,-190.24 917.58,-179.82
909.55,-186.73 915.61,-190.24"/>
-</g>
-<!-- server -->
-<g id="node15" class="node">
-<title>server</title>
-<ellipse fill="none" stroke="black" cx="625.29" cy="-450" rx="32.49" ry="18"/>
-<text text-anchor="middle" x="625.29" y="-446.3" font-family="Times,serif"
font-size="14.00">server</text>
-</g>
-<!-- server->arrow_deps -->
-<g id="edge25" class="edge">
-<title>server->arrow_deps</title>
-<path fill="none" stroke="black" d="M658.13,-449.09C711.09,-447.85
817.14,-439.57 893.29,-396 930.46,-374.74 937.93,-362.18 957.29,-324
994.01,-251.6 1025.97,-215.91 988.29,-144 953.67,-77.92 868.89,-45.19
812.51,-30.21"/>
-<polygon fill="black" stroke="black" points="813.23,-26.78 802.67,-27.7
811.5,-33.56 813.23,-26.78"/>
-</g>
-<!-- server->analytic_engine -->
-<g id="edge24" class="edge">
-<title>server->analytic_engine</title>
-<path fill="none" stroke="black" d="M593.23,-446.76C510.79,-440.7
293.19,-422.57 226.29,-396 175.4,-375.79 159.51,-367.54 126.29,-324
95.11,-283.13 78.72,-224.32 71.34,-190.25"/>
-<polygon fill="black" stroke="black" points="74.7,-189.2 69.25,-180.11
67.84,-190.61 74.7,-189.2"/>
-</g>
-<!-- server->table_engine -->
-<g id="edge32" class="edge">
-<title>server->table_engine</title>
-<path fill="none" stroke="black" d="M624.38,-431.73C621.32,-374.19
611.48,-188.66 607.75,-118.35"/>
-<polygon fill="black" stroke="black" points="611.23,-117.89 607.2,-108.09
604.24,-118.27 611.23,-117.89"/>
-</g>
-<!-- server->catalog -->
-<g id="edge26" class="edge">
-<title>server->catalog</title>
-<path fill="none" stroke="black" d="M601.77,-437.48C585.83,-428.43
565.66,-414.29 554.29,-396 513.59,-330.5 509.44,-235.98 510.14,-190.07"/>
-<polygon fill="black" stroke="black" points="513.64,-190.09 510.38,-180.01
506.64,-189.92 513.64,-190.09"/>
-</g>
-<!-- server->system_catalog -->
-<g id="edge31" class="edge">
-<title>server->system_catalog</title>
-<path fill="none" stroke="black" d="M598.77,-439.16C575.77,-429.93
542.2,-414.76 516.29,-396 460.5,-355.59 407.29,-294.09 379.75,-259.99"/>
-<polygon fill="black" stroke="black" points="382.3,-257.57 373.32,-251.94
376.83,-261.93 382.3,-257.57"/>
-</g>
-<!-- server->meta_client -->
-<g id="edge28" class="edge">
-<title>server->meta_client</title>
-<path fill="none" stroke="black" d="M592.89,-447.9C513.12,-443.67
303.95,-423.2 169.29,-324 127.29,-293.06 98.74,-262.04 123.29,-216
131.34,-200.91 145.8,-189.36 160.16,-180.95"/>
-<polygon fill="black" stroke="black" points="161.93,-183.98 169.04,-176.12
158.58,-177.83 161.93,-183.98"/>
-</g>
-<!-- server->interpreters -->
-<g id="edge27" class="edge">
-<title>server->interpreters</title>
-<path fill="none" stroke="black" d="M648.2,-437.13C668.78,-426.45
699.39,-410.58 723.42,-398.12"/>
-<polygon fill="black" stroke="black" points="725.34,-401.07 732.61,-393.36
722.12,-394.85 725.34,-401.07"/>
-</g>
-<!-- server->sql -->
-<g id="edge30" class="edge">
-<title>server->sql</title>
-<path fill="none" stroke="black" d="M631.41,-432.21C644.94,-395.09
677.47,-305.86 693.72,-261.27"/>
-<polygon fill="black" stroke="black" points="697.07,-262.31 697.2,-251.71
690.49,-259.91 697.07,-262.31"/>
-</g>
-<!-- server->df_operator -->
-<g id="edge33" class="edge">
-<title>server->df_operator</title>
-<path fill="none" stroke="black" d="M657.53,-447.64C724.02,-442.85
875.21,-421.26 935.29,-324 960.76,-282.77 960.15,-263.45 950.29,-216
948.42,-206.96 944.92,-197.58 941.21,-189.26"/>
-<polygon fill="black" stroke="black" points="944.29,-187.6 936.84,-180.07
937.97,-190.61 944.29,-187.6"/>
-</g>
-<!-- server->query_engine -->
-<g id="edge29" class="edge">
-<title>server->query_engine</title>
-<path fill="none" stroke="black" d="M658.04,-449.43C701.15,-448.17
776.57,-439.35 820.29,-396 836.54,-379.89 842.45,-354.11 844.49,-334.44"/>
-<polygon fill="black" stroke="black" points="848,-334.47 845.27,-324.23
841.02,-333.94 848,-334.47"/>
-</g>
-<!-- ceresdb -->
-<g id="node16" class="node">
-<title>ceresdb</title>
-<ellipse fill="none" stroke="black" cx="625.29" cy="-522" rx="37.89" ry="18"/>
-<text text-anchor="middle" x="625.29" y="-518.3" font-family="Times,serif"
font-size="14.00">ceresdb</text>
-</g>
-<!-- ceresdb->analytic_engine -->
-<g id="edge45" class="edge">
-<title>ceresdb->analytic_engine</title>
-<path fill="none" stroke="black" d="M587.5,-520.15C456.26,-516.2 28.29,-494.46
28.29,-379 28.29,-379 28.29,-379 28.29,-305 28.29,-263.63 43.53,-217.72
54.71,-189.61"/>
-<polygon fill="black" stroke="black" points="58.05,-190.67 58.6,-180.09
51.57,-188.02 58.05,-190.67"/>
-</g>
-<!-- ceresdb->table_engine -->
-<g id="edge50" class="edge">
-<title>ceresdb->table_engine</title>
-<path fill="none" stroke="black" d="M662.08,-517.62C771,-506.59
1084.29,-467.21 1084.29,-379 1084.29,-379 1084.29,-379 1084.29,-305
1084.29,-221.69 1057.73,-190.04 988.29,-144 937.68,-110.44 767.01,-97.83
671.83,-93.33"/>
-<polygon fill="black" stroke="black" points="671.88,-89.83 661.73,-92.87
671.56,-96.82 671.88,-89.83"/>
-</g>
-<!-- ceresdb->catalog -->
-<g id="edge46" class="edge">
-<title>ceresdb->catalog</title>
-<path fill="none" stroke="black" d="M610.61,-505.32C590.32,-482.83
553.88,-439.32 533.29,-396 500.83,-327.69 503.95,-235.52 508.06,-190.31"/>
-<polygon fill="black" stroke="black" points="511.57,-190.43 509.08,-180.13
504.6,-189.73 511.57,-190.43"/>
-</g>
-<!-- ceresdb->catalog_impls -->
-<g id="edge47" class="edge">
-<title>ceresdb->catalog_impls</title>
-<path fill="none" stroke="black" d="M590.01,-515.18C551.6,-507.89
489.14,-493.18 440.29,-468 368.4,-430.94 297.54,-366.19 261.95,-331.15"/>
-<polygon fill="black" stroke="black" points="264.05,-328.31 254.49,-323.74
259.12,-333.27 264.05,-328.31"/>
-</g>
-<!-- ceresdb->df_operator -->
-<g id="edge51" class="edge">
-<title>ceresdb->df_operator</title>
-<path fill="none" stroke="black" d="M660.81,-515.85C699.02,-509.17
760.57,-495.01 807.29,-468 887.3,-421.75 915.85,-406.6 957.29,-324
978.9,-280.95 981.32,-261.76 966.29,-216 962.93,-205.74 956.73,-195.84
950.25,-187.42"/>
-<polygon fill="black" stroke="black" points="952.83,-185.04 943.78,-179.54
947.42,-189.49 952.83,-185.04"/>
-</g>
-<!-- ceresdb->query_engine -->
-<g id="edge48" class="edge">
-<title>ceresdb->query_engine</title>
-<path fill="none" stroke="black" d="M658.65,-513.15C709.22,-499.26
803.68,-465.05 844.29,-396 855.22,-377.43 854.54,-352.69 851.66,-334.01"/>
-<polygon fill="black" stroke="black" points="855.08,-333.27 849.83,-324.07
848.19,-334.54 855.08,-333.27"/>
-</g>
-<!-- ceresdb->server -->
-<g id="edge49" class="edge">
-<title>ceresdb->server</title>
-<path fill="none" stroke="black" d="M625.29,-503.7C625.29,-495.98
625.29,-486.71 625.29,-478.11"/>
-<polygon fill="black" stroke="black" points="628.79,-478.1 625.29,-468.1
621.79,-478.1 628.79,-478.1"/>
-</g>
-</g>
-</svg>
diff --git a/docs/src/cn/dev/platform.md b/docs/src/cn/dev/platform.md
index 8151c11..cf58663 100644
--- a/docs/src/cn/dev/platform.md
+++ b/docs/src/cn/dev/platform.md
@@ -1,7 +1,7 @@
-| target | OS |
status |
-| :-----------------------: | :---------------: |
:------------------------------------------------------------: |
-| x86_64-unknown-linux-gnu | kernel 4.9+ |
✅ |
-| x86_64-apple-darwin | 10.15+, Catalina+ |
✅ |
-| aarch64-apple-darwin | 11+, Big Sur+ |
✅ |
-| aarch64-unknown-linux-gnu | TBD | tracked on
[#63](https://github.com/CeresDB/horaedb/issues/63) |
-| \*-windows | \* |
❌ |
+| target | OS |
status |
+| :-----------------------: | :---------------: |
:---------------------------------------------------------------------: |
+| x86_64-unknown-linux-gnu | kernel 4.9+ |
✅ |
+| x86_64-apple-darwin | 10.15+, Catalina+ |
✅ |
+| aarch64-apple-darwin | 11+, Big Sur+ |
✅ |
+| aarch64-unknown-linux-gnu | TBD | tracked on
[#63](https://github.com/apache/incubator-horaedb/issues/63) |
+| \*-windows | \* |
❌ |
diff --git a/docs/src/cn/dev/profiling.md b/docs/src/cn/dev/profiling.md
index 75961ed..2463571 100644
--- a/docs/src/cn/dev/profiling.md
+++ b/docs/src/cn/dev/profiling.md
@@ -30,12 +30,12 @@ sudo yum install -y jemalloc-devel ghostscript graphviz
// 开启 malloc prof
export MALLOC_CONF=prof:true
-// 运行 ceresdb-server
-./ceresdb-server ....
+// 运行 horaedb-server
+./horaedb-server ....
// 60s 内存采样数据
curl -L '0:5000/debug/profile/heap/60' > /tmp/heap_profile
-jeprof --show_bytes --pdf /usr/bin/ceresdb-server /tmp/heap_profile >
profile_heap.pdf
+jeprof --show_bytes --pdf /usr/bin/horaedb-server /tmp/heap_profile >
profile_heap.pdf
-jeprof --show_bytes --svg /usr/bin/ceresdb-server /tmp/heap_profile >
profile_heap.svg
+jeprof --show_bytes --svg /usr/bin/horaedb-server /tmp/heap_profile >
profile_heap.svg
```
diff --git a/docs/src/cn/ecosystem/opentsdb.md
b/docs/src/cn/ecosystem/opentsdb.md
index 1547d6f..66f4afb 100644
--- a/docs/src/cn/ecosystem/opentsdb.md
+++ b/docs/src/cn/ecosystem/opentsdb.md
@@ -52,4 +52,4 @@ CREATE TABLE `sys.cpu.nice`(
# 查询
-暂不支持 OpenTSDB 查询，[tracking
issue](https://github.com/CeresDB/horaedb/issues/904)。
+暂不支持 OpenTSDB 查询，[tracking
issue](https://github.com/apache/incubator-horaedb/issues/904)。
diff --git a/docs/src/cn/operation/observability.md
b/docs/src/cn/operation/observability.md
index 6de7e77..7867688 100644
--- a/docs/src/cn/operation/observability.md
+++ b/docs/src/cn/operation/observability.md
@@ -16,11 +16,11 @@ HoraeDB 支持使用 Prometheus 和 Grafana 做自监控。
global:
scrape_interval: 30s
scrape_configs:
- - job_name: ceresdb-server
+ - job_name: horaedb-server
static_configs:
- targets: [your_ip:5440, your_ip:5441]
labels:
- env: ceresdbcluster
+ env: horaedbcluster
```
Prometheus
详细配置见[这里](https://prometheus.io/docs/prometheus/latest/configuration/configuration/)。
@@ -79,7 +79,7 @@ docker run -d --name=grafana -p 3000:3000
grafana/grafana:9.3.6
当导入完成后，你可以看到如下页面：
-<img src="../../resources/images/grafana-ceresdb-dashboard.png" height="400"
width="600"/>
+<img src="../../resources/images/grafana-horaedb-dashboard.png" height="400"
width="600"/>
### Panels
diff --git a/docs/src/cn/operation/system_table.md
b/docs/src/cn/operation/system_table.md
index c817e00..bf5065f 100644
--- a/docs/src/cn/operation/system_table.md
+++ b/docs/src/cn/operation/system_table.md
@@ -18,7 +18,6 @@
```shell
curl --location --request POST 'http://localhost:5000/sql' \
--header 'Content-Type: application/json' \
---header 'x-ceresdb-access-schema: my_schema' \
-d '{
"query": "select * from system.public.tables where
`table_name`=\"my_table\""
}'
@@ -31,8 +30,8 @@ curl --location --request POST 'http://localhost:5000/sql' \
"rows":[
{
"timestamp":0,
- "catalog":"ceresdb",
- "schema":"monitor_trace",
+ "catalog":"horaedb",
+ "schema":"public",
"table_name":"my_table",
"table_id":3298534886446,
"engine":"Analytic"
diff --git a/docs/src/cn/operation/table.md b/docs/src/cn/operation/table.md
index 5c49ec5..be1acd5 100644
--- a/docs/src/cn/operation/table.md
+++ b/docs/src/cn/operation/table.md
@@ -22,7 +22,7 @@ curl --location --request POST 'http://127.0.0.1:5000/sql' \
curl --location --request POST 'http://127.0.0.1:5000/sql' \
--header 'Content-Type: application/json' \
-d '{
- "query": "INSERT INTO demo(t, name, value) VALUES(1651737067000,
'\''ceresdb'\'', 100)"
+ "query": "INSERT INTO demo(t, name, value) VALUES(1651737067000,
'\''horaedb'\'', 100)"
}'
```
diff --git a/docs/src/cn/quick_start.md b/docs/src/cn/quick_start.md
index 0cafed0..497f6e2 100644
--- a/docs/src/cn/quick_start.md
+++ b/docs/src/cn/quick_start.md
@@ -4,7 +4,7 @@
## 启动
-使用 [HoraeDB docker 镜像](https://hub.docker.com/r/ceresdb/ceresdb-server)
是一种最简单的启动方式；如果你还没有安装 Docker，请首先参考
[这里](https://www.docker.com/products/docker-desktop/) 安装 Docker。
+使用 [HoraeDB docker
镜像](https://github.com/apache/incubator-horaedb/pkgs/container/horaedb-server)
是一种最简单的启动方式；如果你还没有安装 Docker，请首先参考
[这里](https://www.docker.com/products/docker-desktop/) 安装 Docker。
> 注意：请选择一个大于等于 v1.0.0 的 tag 镜像。
@@ -15,7 +15,7 @@ docker run -d --name horaedb-server \
-p 8831:8831 \
-p 3307:3307 \
-p 5440:5440 \
- ceresdb/ceresdb-server
+ ghcr.io/apache/horaedb-server:nightly-20231222-f57b3827
```
启动后 HoraeDB 会监听如下端口：
@@ -28,20 +28,20 @@ docker run -d --name horaedb-server \
### 自定义 docker 的配置
-参考如下命令，可以自定义 docker 中 ceresdb-server 的配置，并把数据目录 `/data` 挂载到 docker 母机的硬盘上。
+参考如下命令，可以自定义 docker 中 horaedb-server 的配置，并把数据目录 `/data` 挂载到 docker 母机的硬盘上。
```
-wget -c
https://raw.githubusercontent.com/CeresDB/horaedb/main/docs/minimal.toml -O
ceresdb.toml
+wget -c
https://raw.githubusercontent.com/apache/incubator-horaedb/main/docs/minimal.toml
-O horaedb.toml
-sed -i 's/\/tmp\/ceresdb/\/data/g' ceresdb.toml
+sed -i 's/\/tmp\/horaedb/\/data/g' horaedb.toml
docker run -d --name horaedb-server \
-p 8831:8831 \
-p 3307:3307 \
-p 5440:5440 \
- -v ./ceresdb.toml:/etc/ceresdb/ceresdb.toml \
+ -v ./horaedb.toml:/etc/horaedb/horaedb.toml \
-v ./data:/data \
- ceresdb/ceresdb-server
+ ghcr.io/apache/horaedb-server:nightly-20231222-f57b3827
```
## 写入和查询数据
@@ -68,7 +68,7 @@ ENGINE=Analytic
curl --location --request POST 'http://127.0.0.1:5440/sql' \
-d '
INSERT INTO demo (t, name, value)
- VALUES (1651737067000, "ceresdb", 100)
+ VALUES (1651737067000, "horaedb", 100)
'
```
diff --git a/docs/src/cn/sdk/go.md b/docs/src/cn/sdk/go.md
index 04ae7a0..6eb69c1 100644
--- a/docs/src/cn/sdk/go.md
+++ b/docs/src/cn/sdk/go.md
@@ -3,18 +3,18 @@
## 安装
```
-go get github.com/CeresDB/horaedb-client-go
+go get github.com/apache/incubator-horaedb-client-go
```
-你可以在这里找到最新的版本 [here](https://github.com/CeresDB/horaedb-client-go/tags).
+你可以在这里找到最新的版本
[here](https://github.com/apache/incubator-horaedb-client-go/tags).
## 如何使用
### 初始化客户端
```go
- client, err := ceresdb.NewClient(endpoint, ceresdb.Direct,
- ceresdb.WithDefaultDatabase("public"), // Client所使用的database
+ client, err := horaedb.NewClient(endpoint, horaedb.Direct,
+ horaedb.WithDefaultDatabase("public"), // Client所使用的database
)
```
@@ -45,7 +45,7 @@ HoraeDB 使用 SQL 来管理表格，比如创建表、删除表或者新增列
TIMESTAMP KEY(t)
) ENGINE=Analytic with (enable_ttl=false)`
- req := ceresdb.SQLQueryRequest{
+ req := horaedb.SQLQueryRequest{
Tables: []string{"demo"},
SQL: createTableSQL,
}
@@ -56,7 +56,7 @@ HoraeDB 使用 SQL 来管理表格，比如创建表、删除表或者新增列
```go
dropTableSQL := `DROP TABLE demo`
- req := ceresdb.SQLQueryRequest{
+ req := horaedb.SQLQueryRequest{
Tables: []string{"demo"},
SQL: dropTableSQL,
}
@@ -66,12 +66,12 @@ HoraeDB 使用 SQL 来管理表格，比如创建表、删除表或者新增列
### 构建写入数据
```go
- points := make([]ceresdb.Point, 0, 2)
+ points := make([]horaedb.Point, 0, 2)
for i := 0; i < 2; i++ {
- point, err := ceresdb.NewPointBuilder("demo").
+ point, err := horaedb.NewPointBuilder("demo").
SetTimestamp(now)).
- AddTag("name", ceresdb.NewStringValue("test_tag1")).
- AddField("value", ceresdb.NewDoubleValue(0.4242)).
+ AddTag("name", horaedb.NewStringValue("test_tag1")).
+ AddField("value", horaedb.NewDoubleValue(0.4242)).
Build()
if err != nil {
panic(err)
@@ -83,7 +83,7 @@ HoraeDB 使用 SQL 来管理表格，比如创建表、删除表或者新增列
### 写入数据
```go
- req := ceresdb.WriteRequest{
+ req := horaedb.WriteRequest{
Points: points,
}
resp, err := client.Write(context.Background(), req)
@@ -93,7 +93,7 @@ HoraeDB 使用 SQL 来管理表格，比如创建表、删除表或者新增列
```go
querySQL := `SELECT * FROM demo`
- req := ceresdb.SQLQueryRequest{
+ req := horaedb.SQLQueryRequest{
Tables: []string{"demo"},
SQL: querySQL,
}
@@ -106,4 +106,4 @@ HoraeDB 使用 SQL 来管理表格，比如创建表、删除表或者新增列
## 示例
-你可以在[这里](https://github.com/CeresDB/horaedb-client-go/blob/main/examples/read_write.go)找到完整的示例。
+你可以在[这里](https://github.com/apache/incubator-horaedb-client-go/blob/main/examples/read_write.go)找到完整的示例。
diff --git a/docs/src/cn/sdk/java.md b/docs/src/cn/sdk/java.md
index 276e4e7..c8941b5 100644
--- a/docs/src/cn/sdk/java.md
+++ b/docs/src/cn/sdk/java.md
@@ -18,7 +18,7 @@ Java 8 及以上
</dependency>
```
-最新的版本可以从[这里](https://github.com/CeresDB/horaedb-client-java/blob/main/docs/CHANGELOG.md)获取。
+最新的版本可以从[这里](https://github.com/apache/incubator-horaedb-client-java/blob/main/docs/CHANGELOG.md)获取。
## 初始化客户端
@@ -43,7 +43,7 @@ if (!client.init(opts)) {
- RouteMode： DIRECT/PROXY
这里重点解释下 `RouteMode` 参数，`PROXY` 模式用在客户端和服务端存在网络隔离，请求需要经过转发的场景；`DIRECT`
模式用在客户端和服务端网络连通的场景，节省转发的开销，具有更高的性能。
-更多的参数配置详情见
[configuration](https://github.com/CeresDB/horaedb-client-java/tree/main/docs/configuration.md)。
+更多的参数配置详情见
[configuration](https://github.com/apache/incubator-horaedb-client-java/tree/main/docs/configuration.md)。
注意： HoraeDB 当前仅支持默认的 `public` database , 未来会支持多个 database。
@@ -118,7 +118,7 @@ Assert.assertEquals(0, writeResult.getOk().getFailed());
Assert.assertEquals(0, writeResult.mapOr(-1, WriteOk::getFailed).intValue());
```
-详情见
[write](https://github.com/CeresDB/horaedb-client-java/tree/main/docs/write.md)
+详情见
[write](https://github.com/apache/incubator-horaedb-client-java/tree/main/docs/write.md)
## 数据查询
@@ -149,7 +149,7 @@ final Stream<Row> rowStream = queryOk.stream();
rowStream.forEach(row -> System.out.println(row.toString()));
```
-详情见
[read](https://github.com/CeresDB/horaedb-client-java/tree/main/docs/read.md)
+详情见
[read](https://github.com/apache/incubator-horaedb-client-java/tree/main/docs/read.md)
## 流式读写
@@ -180,4 +180,4 @@ Assert.assertTrue(streamQueryResult.isOk());
Assert.assertEquals(1000, streamQueryResult.getOk().getRowCount());
```
-详情见
[streaming](https://github.com/CeresDB/horaedb-client-java/tree/main/docs/streaming.md)
+详情见
[streaming](https://github.com/apache/incubator-horaedb-client-java/tree/main/docs/streaming.md)
diff --git a/docs/src/cn/sdk/python.md b/docs/src/cn/sdk/python.md
index b999ef8..7094d2c 100644
--- a/docs/src/cn/sdk/python.md
+++ b/docs/src/cn/sdk/python.md
@@ -2,11 +2,11 @@
## 介绍
-[horaedb-client](https://pypi.org/project/ceresdb-client/) 是
[HoraeDB](https://github.com/CeresDB/horaedb) python 客户端.
+[horaedb-client](https://pypi.org/project/ceresdb-client/) 是
[HoraeDB](https://github.com/apache/incubator-horaedb) python 客户端.
-借助于 [PyO3](https://github.com/PyO3)，python 客户端的实现实际上是基于 [rust
客户端](https://github.com/CeresDB/horaedb-client-rs) 的封装。
+借助于 [PyO3](https://github.com/PyO3)，python 客户端的实现实际上是基于 [rust
客户端](https://github.com/apache/incubator-horaedb-client-rs) 的封装。
-本手册将会介绍 python client
的一些基本用法，其中涉及到的完整示例，可以查看[该示例代码](https://github.com/CeresDB/horaedb-client-py/blob/main/examples/read_write.py).
+本手册将会介绍 python client
的一些基本用法，其中涉及到的完整示例，可以查看[该示例代码](https://github.com/apache/incubator-horaedb-client-py/blob/main/examples/read_write.py).
## 环境要求
@@ -18,7 +18,7 @@
pip install ceresdb-client
```
-你可以在这里找到最新的版本 [here](https://github.com/CeresDB/horaedb-client-py/tags).
+你可以在这里找到最新的版本
[here](https://github.com/apache/incubator-horaedb-client-py/tags).
## 初始化客户端
@@ -51,7 +51,7 @@ client = builder.build()
至于 `default_database`，会在执行 RPC 请求时未通过 `RpcContext` 设置 database 的情况下，将被作为目标
database 使用。
-最后，通过配置 `RpcConfig`,
可以管理客户端使用的资源和调整其性能，所有的配置参数可以参考[这里](https://github.com/CeresDB/horaedb-client-py/blob/main/ceresdb_client.pyi).
+最后，通过配置 `RpcConfig`,
可以管理客户端使用的资源和调整其性能，所有的配置参数可以参考[这里](https://github.com/apache/incubator-horaedb-client-py/blob/main/ceresdb_client.pyi).
## 建表
diff --git a/docs/src/cn/sdk/rust.md b/docs/src/cn/sdk/rust.md
index bc648dc..91089a6 100644
--- a/docs/src/cn/sdk/rust.md
+++ b/docs/src/cn/sdk/rust.md
@@ -6,7 +6,7 @@
cargo add ceresdb-client
```
-你可以在这里找到最新的版本 [here](https://github.com/CeresDB/horaedb-client-rs/tags).
+你可以在这里找到最新的版本
[here](https://github.com/apache/incubator-horaedb-client-rs/tags).
## 初始化客户端
@@ -14,13 +14,13 @@ cargo add ceresdb-client
- 创建客户端的 builder，你必须设置 `endpoint` 和 `mode`：
- `endpoint` 是类似 "ip/domain_name:port" 形式的字符串。
- - `mode` 用于指定访问 HoraeDB 服务器的方式，[关于 mode
的详细信息](https://github.com/CeresDB/horaedb-client-rs/blob/main/src/db_client/builder.rs#L20)。
+ - `mode` 用于指定访问 HoraeDB 服务器的方式，[关于 mode
的详细信息](https://github.com/apache/incubator-horaedb-client-rs/blob/main/src/db_client/builder.rs#L20)。
```rust
let mut builder = Builder::new("ip/domain_name:port",
Mode::Direct/Mode::Proxy);
```
-- 创建和设置
`rpc_config`，可以按需进行定义或者直接使用默认值，更多详细参数请参考[这里](https://github.com/CeresDB/horaedb-client-rs/blob/main/src/options.rs)：
+- 创建和设置
`rpc_config`，可以按需进行定义或者直接使用默认值，更多详细参数请参考[这里](https://github.com/apache/incubator-horaedb-client-rs/blob/main/src/options.rs)：
```rust
let rpc_config = RpcConfig {
@@ -52,7 +52,7 @@ let builder = builder.rpc_config(rpc_config);
- 建表:
```rust
-let create_table_sql = r#"CREATE TABLE IF NOT EXISTS ceresdb (
+let create_table_sql = r#"CREATE TABLE IF NOT EXISTS horaedb (
str_tag string TAG,
int_tag int32 TAG,
var_tag varbinary TAG,
@@ -63,7 +63,7 @@ let create_table_sql = r#"CREATE TABLE IF NOT EXISTS ceresdb (
TIMESTAMP KEY(t)) ENGINE=Analytic with
(enable_ttl='false')"#;
let req = SqlQueryRequest {
- tables: vec!["ceresdb".to_string()],
+ tables: vec!["horaedb".to_string()],
sql: create_table_sql.to_string(),
};
@@ -76,9 +76,9 @@ let resp = client
- 删表：
```rust
-let drop_table_sql = "DROP TABLE ceresdb";
+let drop_table_sql = "DROP TABLE horaedb";
let req = SqlQueryRequest {
- tables: vec!["ceresdb".to_string()],
+ tables: vec!["horaedb".to_string()],
sql: drop_table_sql.to_string(),
};
@@ -92,10 +92,10 @@ let resp = client
我们支持使用类似
[InfluxDB](https://awesome.influxdata.com/docs/part-2/influxdb-data-model)
的时序数据模型进行写入。
-- 利用 `PointBuilder` 创建 `point`，`tag value` 和 `field value` 的相关数据结构为
`Value`，[`Value` 的详细信息](detail about
Value](https://github.com/CeresDB/horaedb-client-rs/blob/main/src/model/value.rs：
+- 利用 `PointBuilder` 创建 `point`，`tag value` 和 `field value` 的相关数据结构为
`Value`，[`Value` 的详细信息](detail about
Value](https://github.com/apache/incubator-horaedb-client-rs/blob/main/src/model/value.rs：
```rust
-let test_table = "ceresdb";
+let test_table = "horaedb";
let ts = Local::now().timestamp_millis();
let point = PointBuilder::new(test_table.to_string())
.timestamp(ts)
@@ -125,7 +125,7 @@ let mut write_req = WriteRequest::default();
write_req.add_point(point);
```
-- 创建 `rpc_ctx`，同样地可以按需设置或者使用默认值，`rpc_ctx`
的详细信息请参考[这里](https://github.com/CeresDB/horaedb-client-rs/blob/main/src/rpc_client/mod.rs#L23)：
+- 创建 `rpc_ctx`，同样地可以按需设置或者使用默认值，`rpc_ctx`
的详细信息请参考[这里](https://github.com/apache/incubator-horaedb-client-rs/blob/main/src/rpc_client/mod.rs#L23)：
```rust
let rpc_ctx = RpcContext {
@@ -165,4 +165,4 @@ let resp = client.sql_query(rpc_ctx,
&req).await.expect("Should success to write
## 示例
-你可以在本项目的仓库中找到[完整的例子](https://github.com/CeresDB/horaedb-client-rs/blob/main/examples/read_write.rs)。
+你可以在本项目的仓库中找到[完整的例子](https://github.com/apache/incubator-horaedb-client-rs/blob/main/examples/read_write.rs)。
diff --git a/docs/src/cn/sql/dml/insert.md b/docs/src/cn/sql/dml/insert.md
index a3d0c1e..12acb6f 100644
--- a/docs/src/cn/sql/dml/insert.md
+++ b/docs/src/cn/sql/dml/insert.md
@@ -13,5 +13,5 @@ INSERT [INTO] tbl_name
写入一行数据的示例如下：
```sql
-INSERT INTO demo(`timestamp`, tag1) VALUES(1667374200022, 'ceresdb')
+INSERT INTO demo(`timestamp`, tag1) VALUES(1667374200022, 'horaedb')
```
diff --git a/docs/src/en/about.md b/docs/src/en/about.md
index f368e2e..5536ebb 100644
--- a/docs/src/en/about.md
+++ b/docs/src/en/about.md
@@ -1,10 +1,8 @@
-[](https://github.com/CeresDB/horaedb/actions/workflows/ci.yml)
-[](https://github.com/CeresDB/horaedb/issues)
-[](https://join.slack.com/t/ceresdbcommunity/shared_invite/zt-1dcbv8yq8-Fv8aVUb6ODTL7kxbzs9fnA)
-[](https://hub.docker.com/r/ceresdb/ceresdb-server)
+[](https://github.com/apache/incubator-horaedb/actions/workflows/ci.yml)
+[](https://github.com/apache/incubator-horaedb/issues)
HoraeDB is a high-performance, distributed, cloud native time-series database.
diff --git a/docs/src/en/cluster_deployment/no_meta.md
b/docs/src/en/cluster_deployment/no_meta.md
index 97a72e6..04db40d 100644
--- a/docs/src/en/cluster_deployment/no_meta.md
+++ b/docs/src/en/cluster_deployment/no_meta.md
@@ -263,8 +263,8 @@ After the configs are prepared, what we should to do is to
start HoraeDB contain
Just run the commands below:
```shell
-sudo docker run -d -t --name horaedb_0 -p 5440:5440 -p 8831:8831 -v
$(pwd)/config_0.toml:/etc/ceresdb/ceresdb.toml ceresdb/ceresdb-server
-sudo docker run -d -t --name horaedb_1 -p 15440:15440 -p 18831:18831 -v
$(pwd)/config_1.toml:/etc/ceresdb/ceresdb.toml ceresdb/ceresdb-server
+sudo docker run -d -t --name horaedb_0 -p 5440:5440 -p 8831:8831 -v
$(pwd)/config_0.toml:/etc/horaedb/horaedb.toml horaedb/horaedb-server
+sudo docker run -d -t --name horaedb_1 -p 15440:15440 -p 18831:18831 -v
$(pwd)/config_1.toml:/etc/horaedb/horaedb.toml horaedb/horaedb-server
```
After the two containers are created and starting running, read and write
requests can be served by the two-instances HoraeDB cluster.
diff --git a/docs/src/en/cluster_deployment/with_meta.md
b/docs/src/en/cluster_deployment/with_meta.md
index 4c9a5cc..e6439f9 100644
--- a/docs/src/en/cluster_deployment/with_meta.md
+++ b/docs/src/en/cluster_deployment/with_meta.md
@@ -11,13 +11,13 @@ HoraeMeta is one of the core services of HoraeDB
distributed mode, it is used to
### Build
- Golang version >= 1.19.
-- run `make build` in root path of
[HoraeMeta](https://github.com/CeresDB/horaemeta).
+- run `make build` in root path of
[HoraeMeta](https://github.com/apache/incubator-horaedb-meta).
### Deploy
#### Config
-At present, HoraeMeta supports specifying service startup configuration in two
ways: configuration file and environment variable. We provide an example of
configuration file startup. For details, please refer to
[config](https://github.com/CeresDB/horaemeta/tree/main/config). The
configuration priority of environment variables is higher than that of
configuration files. When they exist at the same time, the environment
variables shall prevail.
+At present, HoraeMeta supports specifying service startup configuration in two
ways: configuration file and environment variable. We provide an example of
configuration file startup. For details, please refer to
[config](https://github.com/apache/incubator-horaedb-meta/tree/main/config).
The configuration priority of environment variables is higher than that of
configuration files. When they exist at the same time, the environment
variables shall prevail.
#### Dynamic or Static
@@ -36,29 +36,29 @@ HoraeMeta is based on etcd to achieve high availability. In
product environment,
```bash
docker run -d --name horaemeta-server \
-p 2379:2379 \
- ceresdb/ceresmeta-server:latest
+ ghcr.io/apache/horaemeta-server:nightly-20231225-ab067bf0
```
- Cluster
```bash
-wget
https://raw.githubusercontent.com/CeresDB/docs/main/docs/src/resources/config-ceresmeta-cluster0.toml
+wget
https://raw.githubusercontent.com/apache/incubator-horaedb-docs/main/docs/src/resources/config-horaemeta-cluster0.toml
docker run -d --network=host --name horaemeta-server0 \
- -v $(pwd)/config-ceresmeta-cluster0.toml:/etc/ceresmeta/ceresmeta.toml \
- ceresdb/ceresmeta-server:latest
+ -v $(pwd)/config-horaemeta-cluster0.toml:/etc/horaemeta/horaemeta.toml \
+ ghcr.io/apache/horaemeta-server:nightly-20231225-ab067bf0
-wget
https://raw.githubusercontent.com/CeresDB/docs/main/docs/src/resources/config-ceresmeta-cluster1.toml
+wget
https://raw.githubusercontent.com/apache/incubator-horaedb-docs/main/docs/src/resources/config-horaemeta-cluster1.toml
docker run -d --network=host --name horaemeta-server1 \
- -v $(pwd)/config-ceresmeta-cluster1.toml:/etc/ceresmeta/ceresmeta.toml \
- ceresdb/ceresmeta-server:latest
+ -v $(pwd)/config-horaemeta-cluster1.toml:/etc/horaemeta/horaemeta.toml \
+ ghcr.io/apache/horaemeta-server:nightly-20231225-ab067bf0
-wget
https://raw.githubusercontent.com/CeresDB/docs/main/docs/src/resources/config-ceresmeta-cluster2.toml
+wget
https://raw.githubusercontent.com/apache/incubator-horaedb-docs/main/docs/src/resources/config-horaemeta-cluster2.toml
docker run -d --network=host --name horaemeta-server2 \
- -v $(pwd)/config-ceresmeta-cluster2.toml:/etc/ceresmeta/ceresmeta.toml \
- ceresdb/ceresmeta-server:latest
+ -v $(pwd)/config-horaemeta-cluster2.toml:/etc/horaemeta/horaemeta.toml \
+ ghcr.io/apache/horaemeta-server:nightly-20231225-ab067bf0
```
And if the storage used by the HoraeDB is remote and you want to enable the
dynamic schedule features of the HoraeDB cluster, the `-e
TOPOLOGY_TYPE=dynamic` can be added to the docker run command.
@@ -75,7 +75,7 @@ The relevant storage configurations include two parts:
Note: If you are deploying HoraeDB over multiple nodes in a production
environment, please set the environment variable for the server address as
follows:
```shell
-export CERESDB_SERVER_ADDR="{server_address}:8831"
+export HORAEDB_SERVER_ADDR="{server_address}:8831"
```
This address is used for communication between HoraeMeta and HoraeDB, please
ensure it is valid.
@@ -89,7 +89,7 @@ Similarly, we can configure HoraeDB to use a local disk as
the underlying storag
```toml
[analytic.storage.object_store]
type = "Local"
-data_dir = "/home/admin/data/ceresdb"
+data_dir = "/home/admin/data/horaedb"
```
#### OSS
@@ -130,7 +130,7 @@ The WAL based on RocksDB is also a kind of local storage
for HoraeDB, which is e
```toml
[analytic.wal]
type = "RocksDB"
-data_dir = "/home/admin/data/ceresdb"
+data_dir = "/home/admin/data/horaedb"
```
#### OceanBase
@@ -229,7 +229,7 @@ store_timeout = "5s"
[analytic.wal]
type = "RocksDB"
-data_dir = "/home/admin/data/ceresdb"
+data_dir = "/home/admin/data/horaedb"
[analytic.storage]
mem_cache_capacity = "20GB"
@@ -238,7 +238,7 @@ mem_cache_partition_bits = 8
[analytic.storage.object_store]
type = "Local"
-data_dir = "/home/admin/data/ceresdb/"
+data_dir = "/home/admin/data/horaedb/"
[analytic.table_opts]
arena_block_size = 2097152
@@ -264,27 +264,8 @@ Firstly, let's start the HoraeMeta:
```bash
docker run -d --name horaemeta-server \
-p 2379:2379 \
- ceresdb/ceresmeta-server
+ ghcr.io/apache/horaemeta-server:nightly-20231225-ab067bf0
```
With the started HoraeMeta cluster, let's start the HoraeDB instance:
-
-```bash
-wget
https://raw.githubusercontent.com/CeresDB/docs/main/docs/src/resources/config-ceresdb-cluster0.toml
-
-docker run -d --name horaedb-server0 \
- -p 5440:5440 \
- -p 8831:8831 \
- -p 3307:3307 \
- -v $(pwd)/config-ceresdb-cluster0.toml:/etc/ceresdb/ceresdb.toml \
- ceresdb/ceresdb-server
-
-wget
https://raw.githubusercontent.com/CeresDB/docs/main/docs/src/resources/config-ceresdb-cluster1.toml
-
-docker run -d --name horaedb-server1 \
- -p 5441:5441 \
- -p 8832:8832 \
- -p 13307:13307 \
- -v $(pwd)/config-ceresdb-cluster1.toml:/etc/ceresdb/ceresdb.toml \
- ceresdb/ceresdb-server
-```
+TODO: complete it later
diff --git a/docs/src/en/design/architecture.md
b/docs/src/en/design/architecture.md
index ba42099..eb5cd7e 100644
--- a/docs/src/en/design/architecture.md
+++ b/docs/src/en/design/architecture.md
@@ -58,7 +58,7 @@ The figure above shows the architecture of HoraeDB
stand-alone service and the d
### RPC Layer
-module path: https://github.com/CeresDB/horaedb/tree/main/server
+module path: https://github.com/apache/incubator-horaedb/tree/main/server
The current RPC supports multiple protocols including HTTP, gRPC, MySQL.
@@ -66,7 +66,7 @@ Basically, HTTP and MySQL are used to debug HoraeDB, query
manually and perform
### SQL Layer
-module path: https://github.com/CeresDB/horaedb/tree/main/query_frontend
+module path:
https://github.com/apache/incubator-horaedb/tree/main/query_frontend
SQL layer takes responsibilities for parsing sql and generating the query plan.
@@ -74,13 +74,13 @@ Based on
[sqlparser](https://github.com/sqlparser-rs/sqlparser-rs) a sql dialect
### Interpreter
-module path: https://github.com/CeresDB/horaedb/tree/main/interpreters
+module path: https://github.com/apache/incubator-horaedb/tree/main/interpreters
The `Interpreter` module encapsulates the SQL `CRUD` operations. In the query
procedure, a sql received by HoraeDB is parsed, converted into the query plan
and then executed in some specific interpreter, such as `SelectInterpreter`,
`InsertInterpreter` and etc.
### Catalog
-module path: https://github.com/CeresDB/horaedb/tree/main/catalog_impls
+module path:
https://github.com/apache/incubator-horaedb/tree/main/catalog_impls
`Catalog` is actually the module managing metadata and the levels of metadata
adopted by HoraeDB is similar to PostgreSQL: `Catalog > Schema > Table`, but
they are only used as namespace.
@@ -88,7 +88,7 @@ At present, `Catalog` and `Schema` have two different kinds
of implementation fo
### Query Engine
-module path: https://github.com/CeresDB/horaedb/tree/main/query_engine
+module path: https://github.com/apache/incubator-horaedb/tree/main/query_engine
`Query Engine` is responsible for optimizing and executing query plan given a
basic SQL plan provided by SQL layer and now such work is mainly delegated to
[DataFusion](https://github.com/apache/arrow-datafusion).
@@ -96,7 +96,7 @@ In addition to the basic functions of SQL, HoraeDB also
defines some customized
### Pluggable Table Engine
-module path: https://github.com/CeresDB/horaedb/tree/main/table_engine
+module path: https://github.com/apache/incubator-horaedb/tree/main/table_engine
`Table Engine` is actually a storage engine for managing tables in HoraeDB and
the pluggability of `Table Engine` is a core design of HoraeDB which matters in
achieving our long-term target, e.g supporting handle log or tracing workload
by implementing new storage engines. HoraeDB will have multiple kinds of `Table
Engine` for different workloads and the most appropriate one should be chosen
as the storage engine according to the workload pattern.
@@ -117,7 +117,7 @@ The following part gives a description about details of
`Analytic Table Engine`.
#### WAL
-module path: https://github.com/CeresDB/horaedb/tree/main/wal
+module path: https://github.com/apache/incubator-horaedb/tree/main/wal
The model of HoraeDB processing data is `WAL` + `MemTable` that the recent
written data is written to `WAL` first and then to `MemTable` and after a
certain amount of data in `MemTable` is accumulated, the data will be organized
in a query-friendly form to persistent devices.
@@ -129,15 +129,15 @@ Now three implementations of `WAL` are provided for
standalone and distributed m
#### MemTable
-module path:
https://github.com/CeresDB/horaedb/tree/main/analytic_engine/src/memtable
+module path:
https://github.com/apache/incubator-horaedb/tree/main/analytic_engine/src/memtable
For `WAL` can't provide efficient data retrieval, the newly written data is
also stored in `Memtable` for efficient data retrieval, after a certain amount
of data is reached, HoraeDB organizes the data in `MemTable` into a
query-friendly storage format (`SST`) and stores it to the persistent device.
-The current implementation of `MemTable` is based on [agatedb's
skiplist](https://github.com/tikv/agatedb/blob/8510bff2bfde5b766c3f83cf81c00141967d48a4/skiplist).
It allows concurrent reads and writes and can control memory usage based on
[Arena](https://github.com/CeresDB/horaedb/tree/main/components/skiplist).
+The current implementation of `MemTable` is based on [agatedb's
skiplist](https://github.com/tikv/agatedb/blob/8510bff2bfde5b766c3f83cf81c00141967d48a4/skiplist).
It allows concurrent reads and writes and can control memory usage based on
[Arena](https://github.com/apache/incubator-horaedb/tree/main/components/skiplist).
#### Flush
-module path:
https://github.com/CeresDB/horaedb/blob/main/analytic_engine/src/instance/flush_compaction.rs
+module path:
https://github.com/apache/incubator-horaedb/blob/main/analytic_engine/src/instance/flush_compaction.rs
What `Flush` does is that when the memory usage of `MemTable` reaches the
threshold, some `MemTables` are selected for flushing into query-friendly
`SST`s saved on persistent device.
@@ -145,13 +145,13 @@ During the flushing procedure, the data will be divided
by a certain time range
#### Compaction
-module path:
https://github.com/CeresDB/horaedb/tree/main/analytic_engine/src/compaction
+module path:
https://github.com/apache/incubator-horaedb/tree/main/analytic_engine/src/compaction
The data of `MemTable` is flushed as `SST`s, but the file size of recently
flushed `SST` may be very small. And too small or too many `SST`s lead to the
poor query performance. Therefore, `Compaction` is then introduced to rearrange
the `SST`s so that the multiple smaller `SST` files can be compacted into a
larger `SST` file.
#### Manifest
-module path:
https://github.com/CeresDB/horaedb/tree/main/analytic_engine/src/meta
+module path:
https://github.com/apache/incubator-horaedb/tree/main/analytic_engine/src/meta
`Manifest` takes responsibilities for managing tables' metadata of `Analytic
Engine` including:
@@ -163,7 +163,7 @@ Now the `Manifest` is based on `WAL` and `Object Storage`.
The newly written upd
#### Object Storage
-module path:
https://github.com/CeresDB/horaedb/tree/main/components/object_store
+module path:
https://github.com/apache/incubator-horaedb/tree/main/components/object_store
The `SST` generated by `Flush` needs to be persisted and the abstraction of
the persistent storage device is `ObjectStore` including multiple
implementations:
@@ -174,7 +174,7 @@ The distributed architecture of HoraeDB separates storage
and computing, which r
#### SST
-module path:
https://github.com/CeresDB/horaedb/tree/main/analytic_engine/src/sst
+module path:
https://github.com/apache/incubator-horaedb/tree/main/analytic_engine/src/sst
`SST` is actually an abstraction that can have multiple specific
implementations. The current implementation is based on
[Parquet](https://parquet.apache.org/), which is a column-oriented data file
format designed for efficient data storage and retrieval.
@@ -182,7 +182,7 @@ The format of `SST` is very critical for retrieving data
and is also the most im
#### Space
-module path:
https://github.com/CeresDB/horaedb/blob/main/analytic_engine/src/space.rs
+module path:
https://github.com/apache/incubator-horaedb/blob/main/analytic_engine/src/space.rs
In `Analytic Engine`, there is a concept called `space` and here is an
explanation for it to resolve some ambiguities when read source code. Actually
`Analytic Engine` does not have the concept of `catalog` and `schema` and only
provides two levels of relationship: `space` and `table`. And in the
implementation, the `schema id` (which should be unique across all `catalog`s)
on the upper layer is actually mapped to `space id`.
@@ -250,7 +250,7 @@ Here are the details:
- `SelectInterpreter` gets the results and feeds them to the protocol module;
- After the protocol layer converts the results, the server module responds to
the client with them.
-The following is the flow of function calls in version
[v1.2.2](https://github.com/CeresDB/horaedb/releases/tag/v1.2.2):
+The following is the flow of function calls in version
[v1.2.2](https://github.com/apache/incubator-horaedb/releases/tag/v1.2.2):
```
┌───────────────────────◀─────────────┐ ┌───────────────────────┐
diff --git a/docs/src/en/design/table_partitioning.md
b/docs/src/en/design/table_partitioning.md
index adf6793..2f34e12 100644
--- a/docs/src/en/design/table_partitioning.md
+++ b/docs/src/en/design/table_partitioning.md
@@ -69,9 +69,9 @@ Refer to [MySQL key
partitioning](https://dev.mysql.com/doc/refman/5.7/en/partit
Since the partition table data is actually stored in different physical
tables, it is necessary to calculate the actual requested physical table
according to the query request when querying.
-The query will calculate the physical table to be queried according to the
query parameters, and then remotely request the node where the physical table
is located to obtain data through the HoraeDB internal service [remote
engine](https://github.com/CeresDB/horaedb/blob/89dca646c627de3cee2133e8f3df96d89854c1a3/server/src/grpc/remote_engine_service/mod.rs)
(support predicate pushdown).
+The query will calculate the physical table to be queried according to the
query parameters, and then remotely request the node where the physical table
is located to obtain data through the HoraeDB internal service [remote
engine](https://github.com/apache/incubator-horaedb/blob/89dca646c627de3cee2133e8f3df96d89854c1a3/server/src/grpc/remote_engine_service/mod.rs)
(support predicate pushdown).
-The implementation of the partition table is in
[PartitionTableImpl](https://github.com/CeresDB/horaedb/blob/89dca646c627de3cee2133e8f3df96d89854c1a3/analytic_engine/src/table/partition.rs).
+The implementation of the partition table is in
[PartitionTableImpl](https://github.com/apache/incubator-horaedb/blob/89dca646c627de3cee2133e8f3df96d89854c1a3/analytic_engine/src/table/partition.rs).
- Step 1: Parse query sql and calculate the physical table to be queried
according to the query parameters.
- Step 2: Query data of physical table.
@@ -105,7 +105,7 @@ The implementation of the partition table is in
[PartitionTableImpl](https://git
- Filters like `and`, `or`, `in`, `=` will choose specific SubTables.
- Fuzzy matching filters like `<`, `>` are also supported, but may have poor
performance since it will scan all physical tables.
-`Key partitioning` rule is implemented in
[KeyRule](https://github.com/CeresDB/horaedb/blob/89dca646c627de3cee2133e8f3df96d89854c1a3/table_engine/src/partition/rule/key.rs).
+`Key partitioning` rule is implemented in
[KeyRule](https://github.com/apache/incubator-horaedb/blob/89dca646c627de3cee2133e8f3df96d89854c1a3/table_engine/src/partition/rule/key.rs).
## Write
diff --git a/docs/src/en/dev/compile_run.md b/docs/src/en/dev/compile_run.md
index 7cd75e1..6065b32 100644
--- a/docs/src/en/dev/compile_run.md
+++ b/docs/src/en/dev/compile_run.md
@@ -53,5 +53,5 @@ cargo build --release
Then you can run HoraeDB using the default configuration file provided in the
codebase.
```bash
-./target/release/ceresdb-server --config ./docs/minimal.toml
+./target/release/horaedb-server --config ./docs/minimal.toml
```
diff --git a/docs/src/en/dev/conventional_commit.md
b/docs/src/en/dev/conventional_commit.md
index 7093989..295a288 100644
--- a/docs/src/en/dev/conventional_commit.md
+++ b/docs/src/en/dev/conventional_commit.md
@@ -53,4 +53,4 @@ But you don't need to add a scope every time. This isn't
mandatory. It's just a
# After all
-There are many other rules or scenarios in [conventional
commit](https://www.conventionalcommits.org/en/v1.0.0/)'s website. We are still
exploring a better and more friendly workflow. Please do let us know by [open
an issue](https://github.com/CeresDB/horaedb/issues/new/choose) if you have any
suggestions ❤️
+There are many other rules or scenarios in [conventional
commit](https://www.conventionalcommits.org/en/v1.0.0/)'s website. We are still
exploring a better and more friendly workflow. Please do let us know by [open
an issue](https://github.com/apache/incubator-horaedb/issues/new/choose) if you
have any suggestions ❤️
diff --git a/docs/src/en/dev/crate-deps.dot b/docs/src/en/dev/crate-deps.dot
deleted file mode 100644
index 45fcd8e..0000000
--- a/docs/src/en/dev/crate-deps.dot
+++ /dev/null
@@ -1,89 +0,0 @@
-// Licensed to the Apache Software Foundation (ASF) under one
-// or more contributor license agreements. See the NOTICE file
-// distributed with this work for additional information
-// regarding copyright ownership. The ASF licenses this file
-// to you under the Apache License, Version 2.0 (the
-// "License"); you may not use this file except in compliance
-// with the License. You may obtain a copy of the License at
-//
-// http://www.apache.org/licenses/LICENSE-2.0
-//
-// Unless required by applicable law or agreed to in writing,
-// software distributed under the License is distributed on an
-// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-// KIND, either express or implied. See the License for the
-// specific language governing permissions and limitations
-// under the License.
-
-// to update svg, run:
-// ```bash
-// dot -Tsvg crate-deps.dot > ./crate-deps.svg
-// ```
-
-digraph G {
-
- arrow_deps
-
- analytic_engine -> arrow_deps
- analytic_engine -> proto
- analytic_engine -> table_engine
- analytic_engine -> wal
-
- catalog -> table_engine
-
- catalog_impls -> catalog
- catalog_impls -> system_catalog
- catalog_impls -> table_engine
- catalog_impls -> cluster
- catalog_impls -> meta_client
-
- cluster -> analytic_engine
- cluster -> catalog
- cluster -> meta_client
-
- interpreters -> catalog
- interpreters -> sql
- interpreters -> table_engine
- interpreters -> df_operator
- interpreters -> query_engine
- interpreters -> arrow_deps
-
- query_engine -> arrow_deps
- query_engine -> sql
- query_engine -> table_engine
- query_engine -> df_operator
-
- server -> analytic_engine
- server -> arrow_deps
- server -> catalog
- server -> interpreters
- server -> meta_client
- server -> query_engine
- server -> sql
- server -> system_catalog
- server -> table_engine
- server -> df_operator
-
- sql -> arrow_deps
- sql -> catalog
- sql -> table_engine
- sql -> df_operator
-
- system_catalog -> arrow_deps
- system_catalog -> catalog
- system_catalog -> proto
- system_catalog -> table_engine
-
- table_engine -> arrow_deps
- table_engine -> proto
-
- df_operator -> arrow_deps
-
- horaedb -> analytic_engine
- horaedb -> catalog
- horaedb -> catalog_impls
- horaedb -> query_engine
- horaedb -> server
- horaedb -> table_engine
- horaedb -> df_operator
-}
diff --git a/docs/src/en/dev/crate-deps.svg b/docs/src/en/dev/crate-deps.svg
deleted file mode 100644
index 6e87508..0000000
--- a/docs/src/en/dev/crate-deps.svg
+++ /dev/null
@@ -1,415 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN"
- "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
-<!-- Generated by graphviz version 3.0.0 (0)
- -->
-<!-- Title: G Pages: 1 -->
-<svg width="1092pt" height="548pt"
- viewBox="0.00 0.00 1092.29 548.00" xmlns="http://www.w3.org/2000/svg";
xmlns:xlink="http://www.w3.org/1999/xlink";>
-<g id="graph0" class="graph" transform="scale(1 1) rotate(0) translate(4 544)">
-<title>G</title>
-<polygon fill="white" stroke="transparent" points="-4,4 -4,-544 1088.29,-544
1088.29,4 -4,4"/>
-<!-- arrow_deps -->
-<g id="node1" class="node">
-<title>arrow_deps</title>
-<ellipse fill="none" stroke="black" cx="758.29" cy="-18" rx="51.99" ry="18"/>
-<text text-anchor="middle" x="758.29" y="-14.3" font-family="Times,serif"
font-size="14.00">arrow_deps</text>
-</g>
-<!-- analytic_engine -->
-<g id="node2" class="node">
-<title>analytic_engine</title>
-<ellipse fill="none" stroke="black" cx="66.29" cy="-162" rx="66.09" ry="18"/>
-<text text-anchor="middle" x="66.29" y="-158.3" font-family="Times,serif"
font-size="14.00">analytic_engine</text>
-</g>
-<!-- analytic_engine->arrow_deps -->
-<g id="edge1" class="edge">
-<title>analytic_engine->arrow_deps</title>
-<path fill="none" stroke="black" d="M104.49,-147.15C159.77,-127.62
265.59,-92.13 358.29,-72 477.37,-46.15 619.29,-30.96 698.05,-23.88"/>
-<polygon fill="black" stroke="black" points="698.61,-27.34 708.27,-22.97
698,-20.37 698.61,-27.34"/>
-</g>
-<!-- proto -->
-<g id="node3" class="node">
-<title>proto</title>
-<ellipse fill="none" stroke="black" cx="282.29" cy="-18" rx="29.5" ry="18"/>
-<text text-anchor="middle" x="282.29" y="-14.3" font-family="Times,serif"
font-size="14.00">proto</text>
-</g>
-<!-- analytic_engine->proto -->
-<g id="edge2" class="edge">
-<title>analytic_engine->proto</title>
-<path fill="none" stroke="black" d="M65.02,-143.86C64.52,-123.95 66.92,-91.37
85.29,-72 126.14,-28.95 197.92,-19.55 242.63,-18.19"/>
-<polygon fill="black" stroke="black" points="242.9,-21.69 252.84,-18.01
242.78,-14.69 242.9,-21.69"/>
-</g>
-<!-- table_engine -->
-<g id="node4" class="node">
-<title>table_engine</title>
-<ellipse fill="none" stroke="black" cx="606.29" cy="-90" rx="55.79" ry="18"/>
-<text text-anchor="middle" x="606.29" y="-86.3" font-family="Times,serif"
font-size="14.00">table_engine</text>
-</g>
-<!-- analytic_engine->table_engine -->
-<g id="edge3" class="edge">
-<title>analytic_engine->table_engine</title>
-<path fill="none" stroke="black" d="M113.75,-149.42C122.86,-147.43
132.34,-145.52 141.29,-144 283.8,-119.8 452.79,-103.64 542.65,-96.03"/>
-<polygon fill="black" stroke="black" points="543,-99.52 552.68,-95.19
542.42,-92.54 543,-99.52"/>
-</g>
-<!-- wal -->
-<g id="node5" class="node">
-<title>wal</title>
-<ellipse fill="none" stroke="black" cx="121.29" cy="-90" rx="27" ry="18"/>
-<text text-anchor="middle" x="121.29" y="-86.3" font-family="Times,serif"
font-size="14.00">wal</text>
-</g>
-<!-- analytic_engine->wal -->
-<g id="edge4" class="edge">
-<title>analytic_engine->wal</title>
-<path fill="none" stroke="black" d="M79.61,-144.05C86.59,-135.17 95.26,-124.14
102.87,-114.45"/>
-<polygon fill="black" stroke="black" points="105.8,-116.38 109.23,-106.36
100.3,-112.06 105.8,-116.38"/>
-</g>
-<!-- table_engine->arrow_deps -->
-<g id="edge42" class="edge">
-<title>table_engine->arrow_deps</title>
-<path fill="none" stroke="black" d="M637.05,-74.83C660.67,-63.96 693.45,-48.86
718.97,-37.11"/>
-<polygon fill="black" stroke="black" points="720.74,-40.15 728.36,-32.79
717.81,-33.79 720.74,-40.15"/>
-</g>
-<!-- table_engine->proto -->
-<g id="edge43" class="edge">
-<title>table_engine->proto</title>
-<path fill="none" stroke="black" d="M561.24,-79.27C496.78,-65.34 379.41,-39.98
319.56,-27.05"/>
-<polygon fill="black" stroke="black" points="319.94,-23.55 309.42,-24.86
318.46,-30.39 319.94,-23.55"/>
-</g>
-<!-- catalog -->
-<g id="node6" class="node">
-<title>catalog</title>
-<ellipse fill="none" stroke="black" cx="511.29" cy="-162" rx="36.29" ry="18"/>
-<text text-anchor="middle" x="511.29" y="-158.3" font-family="Times,serif"
font-size="14.00">catalog</text>
-</g>
-<!-- catalog->table_engine -->
-<g id="edge5" class="edge">
-<title>catalog->table_engine</title>
-<path fill="none" stroke="black" d="M530.98,-146.5C544.15,-136.79
561.74,-123.83 576.6,-112.88"/>
-<polygon fill="black" stroke="black" points="579.01,-115.45 584.98,-106.7
574.86,-109.82 579.01,-115.45"/>
-</g>
-<!-- catalog_impls -->
-<g id="node7" class="node">
-<title>catalog_impls</title>
-<ellipse fill="none" stroke="black" cx="238.29" cy="-306" rx="59.59" ry="18"/>
-<text text-anchor="middle" x="238.29" y="-302.3" font-family="Times,serif"
font-size="14.00">catalog_impls</text>
-</g>
-<!-- catalog_impls->table_engine -->
-<g id="edge8" class="edge">
-<title>catalog_impls->table_engine</title>
-<path fill="none" stroke="black" d="M244,-287.79C251.14,-268.41 264.94,-236.91
285.29,-216 355.98,-143.41 473.7,-112.15 545.23,-99.31"/>
-<polygon fill="black" stroke="black" points="546.18,-102.7 555.44,-97.55
544.99,-95.8 546.18,-102.7"/>
-</g>
-<!-- catalog_impls->catalog -->
-<g id="edge6" class="edge">
-<title>catalog_impls->catalog</title>
-<path fill="none" stroke="black" d="M293.66,-299.08C335.23,-292.6
392.18,-279.24 435.29,-252 461.03,-235.74 482.68,-208.03 496.2,-187.84"/>
-<polygon fill="black" stroke="black" points="499.15,-189.72 501.66,-179.43
493.28,-185.91 499.15,-189.72"/>
-</g>
-<!-- system_catalog -->
-<g id="node8" class="node">
-<title>system_catalog</title>
-<ellipse fill="none" stroke="black" cx="360.29" cy="-234" rx="65.79" ry="18"/>
-<text text-anchor="middle" x="360.29" y="-230.3" font-family="Times,serif"
font-size="14.00">system_catalog</text>
-</g>
-<!-- catalog_impls->system_catalog -->
-<g id="edge7" class="edge">
-<title>catalog_impls->system_catalog</title>
-<path fill="none" stroke="black" d="M264.77,-289.81C282.19,-279.81
305.22,-266.6 324.3,-255.65"/>
-<polygon fill="black" stroke="black" points="326.1,-258.66 333.03,-250.64
322.61,-252.58 326.1,-258.66"/>
-</g>
-<!-- cluster -->
-<g id="node9" class="node">
-<title>cluster</title>
-<ellipse fill="none" stroke="black" cx="166.29" cy="-234" rx="34.39" ry="18"/>
-<text text-anchor="middle" x="166.29" y="-230.3" font-family="Times,serif"
font-size="14.00">cluster</text>
-</g>
-<!-- catalog_impls->cluster -->
-<g id="edge9" class="edge">
-<title>catalog_impls->cluster</title>
-<path fill="none" stroke="black" d="M221.23,-288.41C211.73,-279.17
199.76,-267.54 189.43,-257.49"/>
-<polygon fill="black" stroke="black" points="191.86,-254.97 182.25,-250.51
186.98,-259.99 191.86,-254.97"/>
-</g>
-<!-- meta_client -->
-<g id="node10" class="node">
-<title>meta_client</title>
-<ellipse fill="none" stroke="black" cx="202.29" cy="-162" rx="51.99" ry="18"/>
-<text text-anchor="middle" x="202.29" y="-158.3" font-family="Times,serif"
font-size="14.00">meta_client</text>
-</g>
-<!-- catalog_impls->meta_client -->
-<g id="edge10" class="edge">
-<title>catalog_impls->meta_client</title>
-<path fill="none" stroke="black" d="M233.95,-287.87C227.79,-263.56
216.45,-218.82 209.14,-190.01"/>
-<polygon fill="black" stroke="black" points="212.5,-189.02 206.65,-180.19
205.72,-190.74 212.5,-189.02"/>
-</g>
-<!-- system_catalog->arrow_deps -->
-<g id="edge38" class="edge">
-<title>system_catalog->arrow_deps</title>
-<path fill="none" stroke="black" d="M367.26,-215.81C375.79,-196.46
391.8,-164.97 413.29,-144 492.45,-66.78 622.88,-36.81 698.66,-25.51"/>
-<polygon fill="black" stroke="black" points="699.57,-28.92 708.98,-24.04
698.58,-21.99 699.57,-28.92"/>
-</g>
-<!-- system_catalog->proto -->
-<g id="edge40" class="edge">
-<title>system_catalog->proto</title>
-<path fill="none" stroke="black" d="M354.04,-215.85C340.43,-178.49
308.01,-89.56 291.83,-45.16"/>
-<polygon fill="black" stroke="black" points="295.07,-43.84 288.36,-35.64
288.5,-46.23 295.07,-43.84"/>
-</g>
-<!-- system_catalog->table_engine -->
-<g id="edge41" class="edge">
-<title>system_catalog->table_engine</title>
-<path fill="none" stroke="black" d="M376.56,-216.26C396.29,-196.74
431.26,-164.54 466.29,-144 494.25,-127.61 528.19,-114.62 555.64,-105.59"/>
-<polygon fill="black" stroke="black" points="556.99,-108.84 565.44,-102.45
554.85,-102.17 556.99,-108.84"/>
-</g>
-<!-- system_catalog->catalog -->
-<g id="edge39" class="edge">
-<title>system_catalog->catalog</title>
-<path fill="none" stroke="black" d="M392.32,-218.15C416.88,-206.77
450.76,-191.06 476.09,-179.32"/>
-<polygon fill="black" stroke="black" points="477.74,-182.41 485.34,-175.03
474.79,-176.06 477.74,-182.41"/>
-</g>
-<!-- cluster->analytic_engine -->
-<g id="edge11" class="edge">
-<title>cluster->analytic_engine</title>
-<path fill="none" stroke="black" d="M146.54,-219.17C132.61,-209.42
113.67,-196.16 97.68,-184.97"/>
-<polygon fill="black" stroke="black" points="99.36,-181.87 89.16,-179.01
95.34,-187.61 99.36,-181.87"/>
-</g>
-<!-- cluster->catalog -->
-<g id="edge12" class="edge">
-<title>cluster->catalog</title>
-<path fill="none" stroke="black" d="M197.83,-226.6C259.9,-214.01
397.99,-185.99 468.33,-171.72"/>
-<polygon fill="black" stroke="black" points="469.09,-175.13 478.2,-169.71
467.7,-168.27 469.09,-175.13"/>
-</g>
-<!-- cluster->meta_client -->
-<g id="edge13" class="edge">
-<title>cluster->meta_client</title>
-<path fill="none" stroke="black" d="M174.83,-216.41C179.02,-208.25
184.18,-198.22 188.89,-189.07"/>
-<polygon fill="black" stroke="black" points="192.11,-190.45 193.57,-179.96
185.89,-187.25 192.11,-190.45"/>
-</g>
-<!-- interpreters -->
-<g id="node11" class="node">
-<title>interpreters</title>
-<ellipse fill="none" stroke="black" cx="760.29" cy="-378" rx="51.19" ry="18"/>
-<text text-anchor="middle" x="760.29" y="-374.3" font-family="Times,serif"
font-size="14.00">interpreters</text>
-</g>
-<!-- interpreters->arrow_deps -->
-<g id="edge19" class="edge">
-<title>interpreters->arrow_deps</title>
-<path fill="none" stroke="black" d="M760.2,-359.73C759.88,-302.19
758.84,-116.66 758.45,-46.35"/>
-<polygon fill="black" stroke="black" points="761.95,-46.07 758.39,-36.09
754.95,-46.11 761.95,-46.07"/>
-</g>
-<!-- interpreters->table_engine -->
-<g id="edge16" class="edge">
-<title>interpreters->table_engine</title>
-<path fill="none" stroke="black" d="M745.76,-360.63C725.94,-337.67
690.29,-293.99 667.29,-252 642.81,-207.29 623.88,-150.7 613.96,-117.9"/>
-<polygon fill="black" stroke="black" points="617.27,-116.72 611.07,-108.13
610.56,-118.71 617.27,-116.72"/>
-</g>
-<!-- interpreters->catalog -->
-<g id="edge14" class="edge">
-<title>interpreters->catalog</title>
-<path fill="none" stroke="black" d="M719.82,-366.76C692.55,-358.43
656.85,-344.64 630.29,-324 604.72,-304.12 553.3,-227.83 527.23,-187.82"/>
-<polygon fill="black" stroke="black" points="530.15,-185.89 521.77,-179.41
524.27,-189.7 530.15,-185.89"/>
-</g>
-<!-- sql -->
-<g id="node12" class="node">
-<title>sql</title>
-<ellipse fill="none" stroke="black" cx="703.29" cy="-234" rx="27" ry="18"/>
-<text text-anchor="middle" x="703.29" y="-230.3" font-family="Times,serif"
font-size="14.00">sql</text>
-</g>
-<!-- interpreters->sql -->
-<g id="edge15" class="edge">
-<title>interpreters->sql</title>
-<path fill="none" stroke="black" d="M753.53,-360.15C743.72,-335.71
725.44,-290.17 713.85,-261.29"/>
-<polygon fill="black" stroke="black" points="717.02,-259.8 710.05,-251.82
710.52,-262.41 717.02,-259.8"/>
-</g>
-<!-- df_operator -->
-<g id="node13" class="node">
-<title>df_operator</title>
-<ellipse fill="none" stroke="black" cx="927.29" cy="-162" rx="51.99" ry="18"/>
-<text text-anchor="middle" x="927.29" y="-158.3" font-family="Times,serif"
font-size="14.00">df_operator</text>
-</g>
-<!-- interpreters->df_operator -->
-<g id="edge17" class="edge">
-<title>interpreters->df_operator</title>
-<path fill="none" stroke="black" d="M810.06,-373.51C844.68,-368.26
888.84,-355.37 913.29,-324 943.3,-285.49 938.99,-224.95 933.14,-190.12"/>
-<polygon fill="black" stroke="black" points="936.57,-189.39 931.32,-180.19
929.68,-190.66 936.57,-189.39"/>
-</g>
-<!-- query_engine -->
-<g id="node14" class="node">
-<title>query_engine</title>
-<ellipse fill="none" stroke="black" cx="845.29" cy="-306" rx="59.29" ry="18"/>
-<text text-anchor="middle" x="845.29" y="-302.3" font-family="Times,serif"
font-size="14.00">query_engine</text>
-</g>
-<!-- interpreters->query_engine -->
-<g id="edge18" class="edge">
-<title>interpreters->query_engine</title>
-<path fill="none" stroke="black" d="M779.58,-361.12C790.91,-351.78
805.42,-339.84 817.92,-329.55"/>
-<polygon fill="black" stroke="black" points="820.29,-332.12 825.79,-323.06
815.84,-326.72 820.29,-332.12"/>
-</g>
-<!-- sql->arrow_deps -->
-<g id="edge34" class="edge">
-<title>sql->arrow_deps</title>
-<path fill="none" stroke="black" d="M707.61,-216.21C717.1,-179.26
739.87,-90.67 751.38,-45.89"/>
-<polygon fill="black" stroke="black" points="754.82,-46.57 753.92,-36.01
748.04,-44.82 754.82,-46.57"/>
-</g>
-<!-- sql->table_engine -->
-<g id="edge36" class="edge">
-<title>sql->table_engine</title>
-<path fill="none" stroke="black" d="M696.73,-216.4C688.99,-197.85
675.04,-167.36 658.29,-144 650.78,-133.52 641.21,-123.14 632.32,-114.39"/>
-<polygon fill="black" stroke="black" points="634.72,-111.84 625.08,-107.44
629.88,-116.89 634.72,-111.84"/>
-</g>
-<!-- sql->catalog -->
-<g id="edge35" class="edge">
-<title>sql->catalog</title>
-<path fill="none" stroke="black" d="M680.13,-224.56C647.68,-212.72
588.27,-191.06 549.29,-176.85"/>
-<polygon fill="black" stroke="black" points="550.44,-173.55 539.84,-173.41
548.04,-180.12 550.44,-173.55"/>
-</g>
-<!-- sql->df_operator -->
-<g id="edge37" class="edge">
-<title>sql->df_operator</title>
-<path fill="none" stroke="black" d="M727.27,-225.51C763.72,-214.12
833.8,-192.22 880.56,-177.6"/>
-<polygon fill="black" stroke="black" points="881.66,-180.93 890.16,-174.6
879.57,-174.25 881.66,-180.93"/>
-</g>
-<!-- df_operator->arrow_deps -->
-<g id="edge44" class="edge">
-<title>df_operator->arrow_deps</title>
-<path fill="none" stroke="black" d="M916.49,-144.29C903.47,-125.1 880.1,-93.48
854.29,-72 837.6,-58.1 816.71,-46.06 798.69,-36.99"/>
-<polygon fill="black" stroke="black" points="800.08,-33.77 789.56,-32.52
797,-40.06 800.08,-33.77"/>
-</g>
-<!-- query_engine->arrow_deps -->
-<g id="edge20" class="edge">
-<title>query_engine->arrow_deps</title>
-<path fill="none" stroke="black" d="M846.21,-287.85C847.64,-247.76
847.07,-145.77 810.29,-72 804.59,-60.55 795.49,-50.02 786.49,-41.41"/>
-<polygon fill="black" stroke="black" points="788.8,-38.77 779.03,-34.65
784.1,-43.96 788.8,-38.77"/>
-</g>
-<!-- query_engine->table_engine -->
-<g id="edge22" class="edge">
-<title>query_engine->table_engine</title>
-<path fill="none" stroke="black" d="M830.54,-288.49C803.07,-258.18
741.58,-192.36 683.29,-144 669.54,-132.59 653.37,-121.18 639.4,-111.9"/>
-<polygon fill="black" stroke="black" points="641.32,-108.96 631.04,-106.4
637.47,-114.82 641.32,-108.96"/>
-</g>
-<!-- query_engine->sql -->
-<g id="edge21" class="edge">
-<title>query_engine->sql</title>
-<path fill="none" stroke="black" d="M815.53,-290.33C791.4,-278.43
757.56,-261.75 733.36,-249.82"/>
-<polygon fill="black" stroke="black" points="734.79,-246.63 724.28,-245.34
731.7,-252.9 734.79,-246.63"/>
-</g>
-<!-- query_engine->df_operator -->
-<g id="edge23" class="edge">
-<title>query_engine->df_operator</title>
-<path fill="none" stroke="black" d="M855.02,-288.15C869.26,-263.49
895.9,-217.37 912.55,-188.53"/>
-<polygon fill="black" stroke="black" points="915.61,-190.24 917.58,-179.82
909.55,-186.73 915.61,-190.24"/>
-</g>
-<!-- server -->
-<g id="node15" class="node">
-<title>server</title>
-<ellipse fill="none" stroke="black" cx="625.29" cy="-450" rx="32.49" ry="18"/>
-<text text-anchor="middle" x="625.29" y="-446.3" font-family="Times,serif"
font-size="14.00">server</text>
-</g>
-<!-- server->arrow_deps -->
-<g id="edge25" class="edge">
-<title>server->arrow_deps</title>
-<path fill="none" stroke="black" d="M658.13,-449.09C711.09,-447.85
817.14,-439.57 893.29,-396 930.46,-374.74 937.93,-362.18 957.29,-324
994.01,-251.6 1025.97,-215.91 988.29,-144 953.67,-77.92 868.89,-45.19
812.51,-30.21"/>
-<polygon fill="black" stroke="black" points="813.23,-26.78 802.67,-27.7
811.5,-33.56 813.23,-26.78"/>
-</g>
-<!-- server->analytic_engine -->
-<g id="edge24" class="edge">
-<title>server->analytic_engine</title>
-<path fill="none" stroke="black" d="M593.23,-446.76C510.79,-440.7
293.19,-422.57 226.29,-396 175.4,-375.79 159.51,-367.54 126.29,-324
95.11,-283.13 78.72,-224.32 71.34,-190.25"/>
-<polygon fill="black" stroke="black" points="74.7,-189.2 69.25,-180.11
67.84,-190.61 74.7,-189.2"/>
-</g>
-<!-- server->table_engine -->
-<g id="edge32" class="edge">
-<title>server->table_engine</title>
-<path fill="none" stroke="black" d="M624.38,-431.73C621.32,-374.19
611.48,-188.66 607.75,-118.35"/>
-<polygon fill="black" stroke="black" points="611.23,-117.89 607.2,-108.09
604.24,-118.27 611.23,-117.89"/>
-</g>
-<!-- server->catalog -->
-<g id="edge26" class="edge">
-<title>server->catalog</title>
-<path fill="none" stroke="black" d="M601.77,-437.48C585.83,-428.43
565.66,-414.29 554.29,-396 513.59,-330.5 509.44,-235.98 510.14,-190.07"/>
-<polygon fill="black" stroke="black" points="513.64,-190.09 510.38,-180.01
506.64,-189.92 513.64,-190.09"/>
-</g>
-<!-- server->system_catalog -->
-<g id="edge31" class="edge">
-<title>server->system_catalog</title>
-<path fill="none" stroke="black" d="M598.77,-439.16C575.77,-429.93
542.2,-414.76 516.29,-396 460.5,-355.59 407.29,-294.09 379.75,-259.99"/>
-<polygon fill="black" stroke="black" points="382.3,-257.57 373.32,-251.94
376.83,-261.93 382.3,-257.57"/>
-</g>
-<!-- server->meta_client -->
-<g id="edge28" class="edge">
-<title>server->meta_client</title>
-<path fill="none" stroke="black" d="M592.89,-447.9C513.12,-443.67
303.95,-423.2 169.29,-324 127.29,-293.06 98.74,-262.04 123.29,-216
131.34,-200.91 145.8,-189.36 160.16,-180.95"/>
-<polygon fill="black" stroke="black" points="161.93,-183.98 169.04,-176.12
158.58,-177.83 161.93,-183.98"/>
-</g>
-<!-- server->interpreters -->
-<g id="edge27" class="edge">
-<title>server->interpreters</title>
-<path fill="none" stroke="black" d="M648.2,-437.13C668.78,-426.45
699.39,-410.58 723.42,-398.12"/>
-<polygon fill="black" stroke="black" points="725.34,-401.07 732.61,-393.36
722.12,-394.85 725.34,-401.07"/>
-</g>
-<!-- server->sql -->
-<g id="edge30" class="edge">
-<title>server->sql</title>
-<path fill="none" stroke="black" d="M631.41,-432.21C644.94,-395.09
677.47,-305.86 693.72,-261.27"/>
-<polygon fill="black" stroke="black" points="697.07,-262.31 697.2,-251.71
690.49,-259.91 697.07,-262.31"/>
-</g>
-<!-- server->df_operator -->
-<g id="edge33" class="edge">
-<title>server->df_operator</title>
-<path fill="none" stroke="black" d="M657.53,-447.64C724.02,-442.85
875.21,-421.26 935.29,-324 960.76,-282.77 960.15,-263.45 950.29,-216
948.42,-206.96 944.92,-197.58 941.21,-189.26"/>
-<polygon fill="black" stroke="black" points="944.29,-187.6 936.84,-180.07
937.97,-190.61 944.29,-187.6"/>
-</g>
-<!-- server->query_engine -->
-<g id="edge29" class="edge">
-<title>server->query_engine</title>
-<path fill="none" stroke="black" d="M658.04,-449.43C701.15,-448.17
776.57,-439.35 820.29,-396 836.54,-379.89 842.45,-354.11 844.49,-334.44"/>
-<polygon fill="black" stroke="black" points="848,-334.47 845.27,-324.23
841.02,-333.94 848,-334.47"/>
-</g>
-<!-- ceresdb -->
-<g id="node16" class="node">
-<title>ceresdb</title>
-<ellipse fill="none" stroke="black" cx="625.29" cy="-522" rx="37.89" ry="18"/>
-<text text-anchor="middle" x="625.29" y="-518.3" font-family="Times,serif"
font-size="14.00">ceresdb</text>
-</g>
-<!-- ceresdb->analytic_engine -->
-<g id="edge45" class="edge">
-<title>ceresdb->analytic_engine</title>
-<path fill="none" stroke="black" d="M587.5,-520.15C456.26,-516.2 28.29,-494.46
28.29,-379 28.29,-379 28.29,-379 28.29,-305 28.29,-263.63 43.53,-217.72
54.71,-189.61"/>
-<polygon fill="black" stroke="black" points="58.05,-190.67 58.6,-180.09
51.57,-188.02 58.05,-190.67"/>
-</g>
-<!-- ceresdb->table_engine -->
-<g id="edge50" class="edge">
-<title>ceresdb->table_engine</title>
-<path fill="none" stroke="black" d="M662.08,-517.62C771,-506.59
1084.29,-467.21 1084.29,-379 1084.29,-379 1084.29,-379 1084.29,-305
1084.29,-221.69 1057.73,-190.04 988.29,-144 937.68,-110.44 767.01,-97.83
671.83,-93.33"/>
-<polygon fill="black" stroke="black" points="671.88,-89.83 661.73,-92.87
671.56,-96.82 671.88,-89.83"/>
-</g>
-<!-- ceresdb->catalog -->
-<g id="edge46" class="edge">
-<title>ceresdb->catalog</title>
-<path fill="none" stroke="black" d="M610.61,-505.32C590.32,-482.83
553.88,-439.32 533.29,-396 500.83,-327.69 503.95,-235.52 508.06,-190.31"/>
-<polygon fill="black" stroke="black" points="511.57,-190.43 509.08,-180.13
504.6,-189.73 511.57,-190.43"/>
-</g>
-<!-- ceresdb->catalog_impls -->
-<g id="edge47" class="edge">
-<title>ceresdb->catalog_impls</title>
-<path fill="none" stroke="black" d="M590.01,-515.18C551.6,-507.89
489.14,-493.18 440.29,-468 368.4,-430.94 297.54,-366.19 261.95,-331.15"/>
-<polygon fill="black" stroke="black" points="264.05,-328.31 254.49,-323.74
259.12,-333.27 264.05,-328.31"/>
-</g>
-<!-- ceresdb->df_operator -->
-<g id="edge51" class="edge">
-<title>ceresdb->df_operator</title>
-<path fill="none" stroke="black" d="M660.81,-515.85C699.02,-509.17
760.57,-495.01 807.29,-468 887.3,-421.75 915.85,-406.6 957.29,-324
978.9,-280.95 981.32,-261.76 966.29,-216 962.93,-205.74 956.73,-195.84
950.25,-187.42"/>
-<polygon fill="black" stroke="black" points="952.83,-185.04 943.78,-179.54
947.42,-189.49 952.83,-185.04"/>
-</g>
-<!-- ceresdb->query_engine -->
-<g id="edge48" class="edge">
-<title>ceresdb->query_engine</title>
-<path fill="none" stroke="black" d="M658.65,-513.15C709.22,-499.26
803.68,-465.05 844.29,-396 855.22,-377.43 854.54,-352.69 851.66,-334.01"/>
-<polygon fill="black" stroke="black" points="855.08,-333.27 849.83,-324.07
848.19,-334.54 855.08,-333.27"/>
-</g>
-<!-- ceresdb->server -->
-<g id="edge49" class="edge">
-<title>ceresdb->server</title>
-<path fill="none" stroke="black" d="M625.29,-503.7C625.29,-495.98
625.29,-486.71 625.29,-478.11"/>
-<polygon fill="black" stroke="black" points="628.79,-478.1 625.29,-468.1
621.79,-478.1 628.79,-478.1"/>
-</g>
-</g>
-</svg>
diff --git a/docs/src/en/dev/platform.md b/docs/src/en/dev/platform.md
index 8151c11..cf58663 100644
--- a/docs/src/en/dev/platform.md
+++ b/docs/src/en/dev/platform.md
@@ -1,7 +1,7 @@
-| target | OS |
status |
-| :-----------------------: | :---------------: |
:------------------------------------------------------------: |
-| x86_64-unknown-linux-gnu | kernel 4.9+ |
✅ |
-| x86_64-apple-darwin | 10.15+, Catalina+ |
✅ |
-| aarch64-apple-darwin | 11+, Big Sur+ |
✅ |
-| aarch64-unknown-linux-gnu | TBD | tracked on
[#63](https://github.com/CeresDB/horaedb/issues/63) |
-| \*-windows | \* |
❌ |
+| target | OS |
status |
+| :-----------------------: | :---------------: |
:---------------------------------------------------------------------: |
+| x86_64-unknown-linux-gnu | kernel 4.9+ |
✅ |
+| x86_64-apple-darwin | 10.15+, Catalina+ |
✅ |
+| aarch64-apple-darwin | 11+, Big Sur+ |
✅ |
+| aarch64-unknown-linux-gnu | TBD | tracked on
[#63](https://github.com/apache/incubator-horaedb/issues/63) |
+| \*-windows | \* |
❌ |
diff --git a/docs/src/en/dev/profiling.md b/docs/src/en/dev/profiling.md
index c6deb19..20d666a 100644
--- a/docs/src/en/dev/profiling.md
+++ b/docs/src/en/dev/profiling.md
@@ -30,12 +30,12 @@ Example:
// enable malloc prof
export MALLOC_CONF=prof:true
-// run ceresdb-server
-./ceresdb-server ....
+// run horaedb-server
+./horaedb-server ....
// 60s cpu sampling data
curl -L '0:5000/debug/profile/heap/60' > /tmp/heap_profile
-jeprof --show_bytes --pdf /usr/bin/ceresdb-server /tmp/heap_profile >
profile_heap.pdf
+jeprof --show_bytes --pdf /usr/bin/horaedb-server /tmp/heap_profile >
profile_heap.pdf
-jeprof --show_bytes --svg /usr/bin/ceresdb-server /tmp/heap_profile >
profile_heap.svg
+jeprof --show_bytes --svg /usr/bin/horaedb-server /tmp/heap_profile >
profile_heap.svg
```
diff --git a/docs/src/en/ecosystem/opentsdb.md
b/docs/src/en/ecosystem/opentsdb.md
index 38e176e..b1d846b 100644
--- a/docs/src/en/ecosystem/opentsdb.md
+++ b/docs/src/en/ecosystem/opentsdb.md
@@ -53,4 +53,4 @@ CREATE TABLE `sys.cpu.nice`(
# Query
-OpenTSDB query protocol is not currently supported, [tracking
issue](https://github.com/CeresDB/horaedb/issues/904).
+OpenTSDB query protocol is not currently supported, [tracking
issue](https://github.com/apache/incubator-horaedb/issues/904).
diff --git a/docs/src/en/operation/observability.md
b/docs/src/en/operation/observability.md
index bc9f493..669fe42 100644
--- a/docs/src/en/operation/observability.md
+++ b/docs/src/en/operation/observability.md
@@ -16,11 +16,11 @@ Two HoraeDB http service are started on localhost:5440 and
localhost:5441.
global:
scrape_interval: 30s
scrape_configs:
- - job_name: ceresdb-server
+ - job_name: horaedb-server
static_configs:
- targets: [your_ip:5440, your_ip:5441]
labels:
- env: ceresdbcluster
+ env: horaedbcluster
```
See details about configuration
[here](https://prometheus.io/docs/prometheus/latest/configuration/configuration/).
@@ -79,7 +79,7 @@ See more details
[here](https://grafana.com/docs/grafana/latest/datasources/prom
After importing the dashboard, you will see the following page:
-<img src="../../resources/images/grafana-ceresdb-dashboard.png" height="400"
width="600"/>
+<img src="../../resources/images/grafana-horaedb-dashboard.png" height="400"
width="600"/>
### Panels
diff --git a/docs/src/en/operation/system_table.md
b/docs/src/en/operation/system_table.md
index bfa7c15..8359d82 100644
--- a/docs/src/en/operation/system_table.md
+++ b/docs/src/en/operation/system_table.md
@@ -19,7 +19,6 @@ Query table information via table_name like this:
```shell
curl --location --request POST 'http://localhost:5000/sql' \
--header 'Content-Type: application/json' \
---header 'x-ceresdb-access-schema: my_schema' \
-d '{
"query": "select * from system.public.tables where
`table_name`=\"my_table\""
}'
@@ -32,8 +31,8 @@ curl --location --request POST 'http://localhost:5000/sql' \
"rows":[
{
"timestamp":0,
- "catalog":"ceresdb",
- "schema":"monitor_trace",
+ "catalog":"horaedb",
+ "schema":"public",
"table_name":"my_table",
"table_id":3298534886446,
"engine":"Analytic"
diff --git a/docs/src/en/operation/table.md b/docs/src/en/operation/table.md
index ddb27e5..031fa95 100644
--- a/docs/src/en/operation/table.md
+++ b/docs/src/en/operation/table.md
@@ -22,7 +22,7 @@ curl --location --request POST 'http://127.0.0.1:5000/sql' \
curl --location --request POST 'http://127.0.0.1:5000/sql' \
--header 'Content-Type: application/json' \
-d '{
- "query": "INSERT INTO demo(t, name, value) VALUES(1651737067000,
'\''ceresdb'\'', 100)"
+ "query": "INSERT INTO demo(t, name, value) VALUES(1651737067000,
'\''horaedb'\'', 100)"
}'
```
diff --git a/docs/src/en/quick_start.md b/docs/src/en/quick_start.md
index a76961c..7b6f99d 100644
--- a/docs/src/en/quick_start.md
+++ b/docs/src/en/quick_start.md
@@ -4,7 +4,7 @@ This page shows you how to get started with HoraeDB quickly.
You'll start a stan
## Start server
-[HoraeDB docker image](https://hub.docker.com/r/ceresdb/ceresdb-server) is the
easiest way to get started, if you haven't installed Docker, go
[there](https://www.docker.com/products/docker-desktop/) to install it first.
+[HoraeDB docker
image](https://github.com/apache/incubator-horaedb/pkgs/container/horaedb-server)
is the easiest way to get started, if you haven't installed Docker, go
[there](https://www.docker.com/products/docker-desktop/) to install it first.
> Note: please choose tag version >= v1.0.0, others are mainly for testing.
@@ -15,7 +15,7 @@ docker run -d --name horaedb-server \
-p 8831:8831 \
-p 3307:3307 \
-p 5440:5440 \
- ceresdb/ceresdb-server
+ ghcr.io/apache/horaedb-server:nightly-20231222-f57b3827
```
HoraeDB will listen three ports when start:
@@ -28,20 +28,20 @@ The easiest to use is HTTP, so sections below will use it
for demo. For producti
### Customize docker configuration
-Refer the command as below, you can customize the configuration of
ceresdb-server in docker, and mount the data directory `/data` to the hard disk
of the docker host machine.
+Refer the command as below, you can customize the configuration of
horaedb-server in docker, and mount the data directory `/data` to the hard disk
of the docker host machine.
```
-wget -c
https://raw.githubusercontent.com/CeresDB/horaedb/main/docs/minimal.toml -O
ceresdb.toml
+wget -c
https://raw.githubusercontent.com/apache/incubator-horaedb/main/docs/minimal.toml
-O horaedb.toml
-sed -i 's/\/tmp\/ceresdb/\/data/g' ceresdb.toml
+sed -i 's/\/tmp\/horaedb/\/data/g' horaedb.toml
docker run -d --name horaedb-server \
-p 8831:8831 \
-p 3307:3307 \
-p 5440:5440 \
- -v ./ceresdb.toml:/etc/ceresdb/ceresdb.toml \
+ -v ./horaedb.toml:/etc/horaedb/horaedb.toml \
-v ./data:/data \
- ceresdb/ceresdb-server
+ ghcr.io/apache/horaedb-server:nightly-20231222-f57b3827
```
## Write and read data
@@ -68,7 +68,7 @@ ENGINE=Analytic
curl --location --request POST 'http://127.0.0.1:5440/sql' \
-d '
INSERT INTO demo (t, name, value)
- VALUES (1651737067000, "ceresdb", 100)
+ VALUES (1651737067000, "horaedb", 100)
'
```
diff --git a/docs/src/en/sdk/go.md b/docs/src/en/sdk/go.md
index 2d1e422..ec34d31 100644
--- a/docs/src/en/sdk/go.md
+++ b/docs/src/en/sdk/go.md
@@ -3,18 +3,18 @@
## Installation
```
-go get github.com/CeresDB/horaedb-client-go
+go get github.com/apache/incubator-horaedb-client-go
```
-You can get latest version
[here](https://github.com/CeresDB/horaedb-client-go/tags).
+You can get latest version
[here](https://github.com/apache/incubator-horaedb-client-go/tags).
## How To Use
### Init HoraeDB Client
```go
- client, err := ceresdb.NewClient(endpoint, ceresdb.Direct,
- ceresdb.WithDefaultDatabase("public"),
+ client, err := horaedb.NewClient(endpoint, horaedb.Direct,
+ horaedb.WithDefaultDatabase("public"),
)
```
@@ -47,7 +47,7 @@ Of course, you can also use `create table` statement to
manage the table more fi
TIMESTAMP KEY(t)
) ENGINE=Analytic with (enable_ttl=false)`
- req := ceresdb.SQLQueryRequest{
+ req := horaedb.SQLQueryRequest{
Tables: []string{"demo"},
SQL: createTableSQL,
}
@@ -58,7 +58,7 @@ Of course, you can also use `create table` statement to
manage the table more fi
```go
dropTableSQL := `DROP TABLE demo`
- req := ceresdb.SQLQueryRequest{
+ req := horaedb.SQLQueryRequest{
Tables: []string{"demo"},
SQL: dropTableSQL,
}
@@ -68,12 +68,12 @@ Of course, you can also use `create table` statement to
manage the table more fi
### How To Build Write Data
```go
- points := make([]ceresdb.Point, 0, 2)
+ points := make([]horaedb.Point, 0, 2)
for i := 0; i < 2; i++ {
- point, err := ceresdb.NewPointBuilder("demo").
+ point, err := horaedb.NewPointBuilder("demo").
SetTimestamp(now).
- AddTag("name", ceresdb.NewStringValue("test_tag1")).
- AddField("value", ceresdb.NewDoubleValue(0.4242)).
+ AddTag("name", horaedb.NewStringValue("test_tag1")).
+ AddField("value", horaedb.NewDoubleValue(0.4242)).
Build()
if err != nil {
panic(err)
@@ -85,7 +85,7 @@ Of course, you can also use `create table` statement to
manage the table more fi
### Write Example
```go
- req := ceresdb.WriteRequest{
+ req := horaedb.WriteRequest{
Points: points,
}
resp, err := client.Write(context.Background(), req)
@@ -95,7 +95,7 @@ Of course, you can also use `create table` statement to
manage the table more fi
```go
querySQL := `SELECT * FROM demo`
- req := ceresdb.SQLQueryRequest{
+ req := horaedb.SQLQueryRequest{
Tables: []string{"demo"},
SQL: querySQL,
}
@@ -108,4 +108,4 @@ Of course, you can also use `create table` statement to
manage the table more fi
## Example
-You can find the complete example
[here](https://github.com/CeresDB/horaedb-client-go/blob/main/examples/read_write.go).
+You can find the complete example
[here](https://github.com/apache/incubator-horaedb-client-go/blob/main/examples/read_write.go).
diff --git a/docs/src/en/sdk/java.md b/docs/src/en/sdk/java.md
index 1a0d888..d3fe0bc 100644
--- a/docs/src/en/sdk/java.md
+++ b/docs/src/en/sdk/java.md
@@ -18,7 +18,7 @@ HoraeDB Client is a high-performance Java client for HoraeDB.
</dependency>
```
-You can get latest version
[here](https://github.com/CeresDB/horaedb-client-java/blob/main/docs/CHANGELOG.md).
+You can get latest version
[here](https://github.com/apache/incubator-horaedb-client-java/blob/main/docs/CHANGELOG.md).
## Init HoraeDB Client
@@ -46,7 +46,7 @@ The initialization requires at least three parameters:
Here is the explanation of `RouteMode`. There are two kinds of `RouteMode`,The
`Direct` mode should be adopted to avoid forwarding overhead if all the servers
are accessible to the client.
However, the `Proxy` mode is the only choice if the access to the servers from
the client must go through a gateway.
-For more configuration options, see
[configuration](https://github.com/CeresDB/horaedb-client-java/tree/main/docs/configuration.md)
+For more configuration options, see
[configuration](https://github.com/apache/incubator-horaedb-client-java/tree/main/docs/configuration.md)
Notice: HoraeDB currently only supports the default database `public` now,
multiple databases will be supported in the future;
@@ -120,7 +120,7 @@ final Result<WriteOk, Err> writeResult = wf.get();
Assert.assertEquals(0, writeResult.mapOr(-1,
WriteOk::getFailed).intValue());
```
-See
[write](https://github.com/CeresDB/horaedb-client-java/tree/main/docs/write.md)
+See
[write](https://github.com/apache/incubator-horaedb-client-java/tree/main/docs/write.md)
## Query Data Example
@@ -151,7 +151,7 @@ final Stream<Row> rowStream = queryOk.stream();
rowStream.forEach(row -> System.out.println(row.toString()));
```
-See
[read](https://github.com/CeresDB/horaedb-client-java/tree/main/docs/read.md)
+See
[read](https://github.com/apache/incubator-horaedb-client-java/tree/main/docs/read.md)
## Stream Write/Read Example
@@ -182,4 +182,4 @@ Assert.assertTrue(streamQueryResult.isOk());
Assert.assertEquals(1000, streamQueryResult.getOk().getRowCount());
```
-See
[streaming](https://github.com/CeresDB/horaedb-client-java/tree/main/docs/streaming.md)
+See
[streaming](https://github.com/apache/incubator-horaedb-client-java/tree/main/docs/streaming.md)
diff --git a/docs/src/en/sdk/python.md b/docs/src/en/sdk/python.md
index 7b37cb8..f90b394 100644
--- a/docs/src/en/sdk/python.md
+++ b/docs/src/en/sdk/python.md
@@ -2,11 +2,11 @@
## Introduction
-[horaedb-client](https://pypi.org/project/ceresdb-client/) is the python
client for [HoraeDB](https://github.com/CeresDB/horaedb).
+[horaedb-client](https://pypi.org/project/ceresdb-client/) is the python
client for [HoraeDB](https://github.com/apache/incubator-horaedb).
-Thanks to [PyO3](https://github.com/PyO3), the python client is actually a
wrapper on the [rust client](https://github.com/CeresDB/horaedb-client-rs).
+Thanks to [PyO3](https://github.com/PyO3), the python client is actually a
wrapper on the [rust
client](https://github.com/apache/incubator-horaedb-client-rs).
-The guide will give a basic introduction to the python client by
[example](https://github.com/CeresDB/horaedb-client-py/blob/main/examples/read_write.py).
+The guide will give a basic introduction to the python client by
[example](https://github.com/apache/incubator-horaedb-client-py/blob/main/examples/read_write.py).
## Requirements
@@ -18,7 +18,7 @@ The guide will give a basic introduction to the python client
by [example](https
pip install ceresdb-client
```
-You can get latest version
[here](https://github.com/CeresDB/horaedb-client-py/tags).
+You can get latest version
[here](https://github.com/apache/incubator-horaedb-client-py/tags).
## Init HoraeDB Client
@@ -51,7 +51,7 @@ The initialization requires at least two parameters:
The `default_database` can be set and will be used if following rpc calling
without setting the database in the `RpcContext`.
-By configuring the `RpcConfig`, resource and performance of the client can be
manipulated, and all of the configurations can be referred at
[here](https://github.com/CeresDB/horaedb-client-py/blob/main/ceresdb_client.pyi).
+By configuring the `RpcConfig`, resource and performance of the client can be
manipulated, and all of the configurations can be referred at
[here](https://github.com/apache/incubator-horaedb-client-py/blob/main/ceresdb_client.pyi).
## Create Table
diff --git a/docs/src/en/sdk/rust.md b/docs/src/en/sdk/rust.md
index aa07b57..48358ab 100644
--- a/docs/src/en/sdk/rust.md
+++ b/docs/src/en/sdk/rust.md
@@ -6,7 +6,7 @@
cargo add ceresdb-client
```
-You can get latest version
[here](https://github.com/CeresDB/horaedb-client-rs/tags).
+You can get latest version
[here](https://github.com/apache/incubator-horaedb-client-rs/tags).
## Init Client
@@ -14,13 +14,13 @@ At first, we need to init the client.
- New builder for the client, and you must set `endpoint` and `mode`:
- `endpoint` is a string which is usually like "ip/domain_name:port".
- - `mode` is used to define the way to access horaedb server, [detail about
mode](https://github.com/CeresDB/horaedb-client-rs/blob/main/src/db_client/builder.rs#L20).
+ - `mode` is used to define the way to access horaedb server, [detail about
mode](https://github.com/apache/incubator-horaedb-client-rs/blob/main/src/db_client/builder.rs#L20).
```rust
let mut builder = Builder::new("ip/domain_name:port",
Mode::Direct/Mode::Proxy);
```
-- New and set `rpc_config`, it can be defined on demand or just use the
default value, [detail about rpc
config](https://github.com/CeresDB/horaedb-client-rs/blob/main/src/options.rs):
+- New and set `rpc_config`, it can be defined on demand or just use the
default value, [detail about rpc
config](https://github.com/apache/incubator-horaedb-client-rs/blob/main/src/options.rs):
```rust
let rpc_config = RpcConfig {
@@ -54,7 +54,7 @@ You can use the sql query interface to create or drop table,
related setting wil
- Create table:
```rust
-let create_table_sql = r#"CREATE TABLE IF NOT EXISTS ceresdb (
+let create_table_sql = r#"CREATE TABLE IF NOT EXISTS horaedb (
str_tag string TAG,
int_tag int32 TAG,
var_tag varbinary TAG,
@@ -65,7 +65,7 @@ let create_table_sql = r#"CREATE TABLE IF NOT EXISTS ceresdb (
TIMESTAMP KEY(t)) ENGINE=Analytic with
(enable_ttl='false')"#;
let req = SqlQueryRequest {
- tables: vec!["ceresdb".to_string()],
+ tables: vec!["horaedb".to_string()],
sql: create_table_sql.to_string(),
};
@@ -78,9 +78,9 @@ let resp = client
- Drop table:
```rust
-let drop_table_sql = "DROP TABLE ceresdb";
+let drop_table_sql = "DROP TABLE horaedb";
let req = SqlQueryRequest {
- tables: vec!["ceresdb".to_string()],
+ tables: vec!["horaedb".to_string()],
sql: drop_table_sql.to_string(),
};
@@ -94,10 +94,10 @@ let resp = client
We support to write with the time series data model like
[InfluxDB](https://awesome.influxdata.com/docs/part-2/influxdb-data-model/).
-- Build the `point` first by `PointBuilder`, the related data structure of
`tag value` and `field value` in it is defined as `Value`, [detail about
Value](https://github.com/CeresDB/horaedb-client-rs/blob/main/src/model/value.rs):
+- Build the `point` first by `PointBuilder`, the related data structure of
`tag value` and `field value` in it is defined as `Value`, [detail about
Value](https://github.com/apache/incubator-horaedb-client-rs/blob/main/src/model/value.rs):
```rust
-let test_table = "ceresdb";
+let test_table = "horaedb";
let ts = Local::now().timestamp_millis();
let point = PointBuilder::new(test_table.to_string())
.timestamp(ts)
@@ -127,7 +127,7 @@ let mut write_req = WriteRequest::default();
write_req.add_point(point);
```
-- New `rpc_ctx`, and it can also be defined on demand or just use the default
value, [detail about rpc
ctx](https://github.com/CeresDB/horaedb-client-rs/blob/a72e673103463c7962e01a097592fc7edbcc0b79/src/rpc_client/mod.rs#L29):
+- New `rpc_ctx`, and it can also be defined on demand or just use the default
value, [detail about rpc
ctx](https://github.com/apache/incubator-horaedb-client-rs/blob/a72e673103463c7962e01a097592fc7edbcc0b79/src/rpc_client/mod.rs#L29):
- Finally, write to server by client.
@@ -160,4 +160,4 @@ let resp = client.sql_query(rpc_ctx,
&req).await.expect("Should success to write
## Example
-You can find the [complete
example](https://github.com/CeresDB/horaedb-client-rs/blob/main/examples/read_write.rs)
in the project.
+You can find the [complete
example](https://github.com/apache/incubator-horaedb-client-rs/blob/main/examples/read_write.rs)
in the project.
diff --git a/docs/src/en/sql/dml/insert.md b/docs/src/en/sql/dml/insert.md
index 200082b..1fc72e9 100644
--- a/docs/src/en/sql/dml/insert.md
+++ b/docs/src/en/sql/dml/insert.md
@@ -13,5 +13,5 @@ INSERT [INTO] tbl_name
`INSERT` inserts new rows into a HoraeDB table. Here is an example:
```sql
-INSERT INTO demo(`time_stammp`, tag1) VALUES(1667374200022, 'ceresdb')
+INSERT INTO demo(`time_stammp`, tag1) VALUES(1667374200022, 'horaedb')
```
diff --git a/docs/src/resources/config-ceresdb-cluster0.toml
b/docs/src/resources/config-horaedb-cluster0.toml
similarity index 100%
rename from docs/src/resources/config-ceresdb-cluster0.toml
rename to docs/src/resources/config-horaedb-cluster0.toml
diff --git a/docs/src/resources/config-ceresdb-cluster1.toml
b/docs/src/resources/config-horaedb-cluster1.toml
similarity index 100%
rename from docs/src/resources/config-ceresdb-cluster1.toml
rename to docs/src/resources/config-horaedb-cluster1.toml
diff --git a/docs/src/resources/config-ceresmeta-cluster0.toml
b/docs/src/resources/config-horaemeta-cluster0.toml
similarity index 100%
rename from docs/src/resources/config-ceresmeta-cluster0.toml
rename to docs/src/resources/config-horaemeta-cluster0.toml
diff --git a/docs/src/resources/config-ceresmeta-cluster1.toml
b/docs/src/resources/config-horaemeta-cluster1.toml
similarity index 100%
rename from docs/src/resources/config-ceresmeta-cluster1.toml
rename to docs/src/resources/config-horaemeta-cluster1.toml
diff --git a/docs/src/resources/config-ceresmeta-cluster2.toml
b/docs/src/resources/config-horaemeta-cluster2.toml
similarity index 100%
rename from docs/src/resources/config-ceresmeta-cluster2.toml
rename to docs/src/resources/config-horaemeta-cluster2.toml
diff --git a/docs/src/resources/config-ceresmeta-standalone.toml
b/docs/src/resources/config-horaemeta-standalone.toml
similarity index 100%
rename from docs/src/resources/config-ceresmeta-standalone.toml
rename to docs/src/resources/config-horaemeta-standalone.toml
diff --git a/docs/src/resources/config_kafka_oss.toml
b/docs/src/resources/config_kafka_oss.toml
index 16486bf..796b72c 100644
--- a/docs/src/resources/config_kafka_oss.toml
+++ b/docs/src/resources/config_kafka_oss.toml
@@ -6,8 +6,8 @@
# And one thing deserves explanation that this config is used for running
horaedb docker container:
# ```
# docker run -d --name horaedb-server \
-# -v /etc/horaedb/ceresdb.toml:{path_to_this_config} \
-# ceresdb/ceresdb-server
+# -v /etc/horaedb/horaedb.toml:{path_to_this_config} \
+# horaedb/horaedb-server
# ```
[server]
@@ -19,7 +19,7 @@ grpc_port = 8831
level = "info"
[tracing]
-dir = "/home/admin/data/ceresdb"
+dir = "/home/admin/data/horaedb"
[runtime]
read_thread_num = 20
diff --git a/docs/src/resources/config_local_oss.toml
b/docs/src/resources/config_local_oss.toml
index 60aae39..d4283af 100644
--- a/docs/src/resources/config_local_oss.toml
+++ b/docs/src/resources/config_local_oss.toml
@@ -5,8 +5,8 @@
# And one thing deserves explanation that this config is used for running
horaedb docker container:
# ```
# docker run -d --name horaedb-server \
-# -v /etc/ceresdb/ceresdb.toml:{path_to_this_config} \
-# ceresdb/ceresdb-server
+# -v /etc/horaedb/horaedb.toml:{path_to_this_config} \
+# horaedb/horaedb-server
# ```
[server]
@@ -18,7 +18,7 @@ grpc_port = 8831
level = "info"
[tracing]
-dir = "/home/admin/data/ceresdb"
+dir = "/home/admin/data/horaedb"
[runtime]
read_thread_num = 20
@@ -52,7 +52,7 @@ store_timeout = "5s"
[analytic.wal]
type = "RocksDB"
-data_dir = "/home/admin/data/ceresdb"
+data_dir = "/home/admin/data/horaedb"
[analytic.storage]
mem_cache_capacity = "20GB"
diff --git a/docs/src/resources/config_obkv_oss.toml
b/docs/src/resources/config_obkv_oss.toml
index 56103f6..965b0d9 100644
--- a/docs/src/resources/config_obkv_oss.toml
+++ b/docs/src/resources/config_obkv_oss.toml
@@ -6,8 +6,8 @@
# And one thing deserves explanation that this config is used for running
horaedb docker container:
# ```
# docker run -d --name horaedb-server \
-# -v /etc/ceresdb/ceresdb.toml:{path_to_this_config} \
-# ceresdb/ceresdb-server
+# -v /etc/horaedb/horaedb.toml:{path_to_this_config} \
+# horaedb/horaedb-server
# ```
[server]
@@ -19,7 +19,7 @@ grpc_port = 8831
level = "info"
[tracing]
-dir = "/home/admin/data/ceresdb"
+dir = "/home/admin/data/horaedb"
[runtime]
read_thread_num = 20
diff --git a/docs/src/resources/grafana-dashboard.json
b/docs/src/resources/grafana-dashboard.json
index 41377b5..e6d6954 100644
--- a/docs/src/resources/grafana-dashboard.json
+++ b/docs/src/resources/grafana-dashboard.json
@@ -1845,7 +1845,7 @@
},
"timepicker": {},
"timezone": "",
- "title": "ceresdb",
+ "title": "horaedb",
"uid": "w3-h_9LVk",
"version": 25,
"weekStart": ""
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
