Skip to content

chore: Address branding of Apache OpenDAL #285

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 27, 2023
Merged

chore: Address branding of Apache OpenDAL #285

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/cn/guides/00-overview/02-community/01-rfcs/20220704-presign.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ MySQL [(none)]> PRESIGN UPLOAD @my_stage/books.csv

`PRESIGN` will be implemented as a statement instead of a function so that we can return the HTTP method, headers, and URL at the same time.

Most jobs have been done via [OpenDAL presign](https://opendal.databend.rs/rfcs/0413-presign.html).
Most jobs have been done via [Apache OpenDAL presign](https://opendal.databend.rs/rfcs/0413-presign.html).

The syntax will be:

Expand Down
8 changes: 4 additions & 4 deletions docs/cn/guides/00-overview/02-community/01-rfcs/20220725-cache.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,13 +34,13 @@ After introducing cache, the databend storage layer will be composed as follows:

![](/img/rfc/20220725-cache/cache.png)

The query will maintain three OpenDAL operators:
The query will maintain three Apache OpenDAL operators:

- `Persist Operator`: Read and write persist data from/into storage services **directly**.
- `Cache Operator`: Read and write data via transparent caching.
- `Temporary Operator`: Read and write temporary data from/into temporary storage which only store data with TTL.

Storage, cache, and temporary services we mentioned here are both OpenDAL-supported services. The difference is:
Storage, cache, and temporary services we mentioned here are both Apache OpenDAL-supported services. The difference is:

- `Persist Services`: All data will be persisted until users delete them.
- `Cache Services`: Backends could have their GC or background auto eviction logic, which means cache services is non-persist, a.k.a, volatile.
Expand Down Expand Up @@ -94,7 +94,7 @@ As discussed before, developers now have three kinds of `Operator` to handle dif

### Cache Operator

`Cache Operator` will be implemented as an [OpenDAL Layer](https://docs.rs/opendal/0.11.2/opendal/trait.Layer.html):
`Cache Operator` will be implemented as an [Apache OpenDAL Layer](https://docs.rs/opendal/0.11.2/opendal/trait.Layer.html):

```rust
#[derive(Clone, Default, Debug)]
Expand Down Expand Up @@ -149,4 +149,4 @@ None.

### OpenCache

[OpenCache](https://github.com/datafuselabs/opencache) is an ongoing work from databend community to build a distributed cache services. OpenDAL will implement native support for `OpenCache` once its API is stable. After that, users can deploy and use OpenCache as `cache` storage.
[OpenCache](https://github.com/datafuselabs/opencache) is an ongoing work from databend community to build a distributed cache services. Apache OpenDAL will implement native support for `OpenCache` once its API is stable. After that, users can deploy and use OpenCache as `cache` storage.
4 changes: 2 additions & 2 deletions docs/cn/guides/10-deploy/11-cluster/11-deploying-databend-on-kubernetes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ import TabItem from '@theme/TabItem';
* 创建一个云对象存储并提供相应的凭证，即 `access_key_id` 和 `secret_access_key`。
* AWS S3 或其他兼容 S3 的存储服务
* Azure 存储 Blob
* 由 [opendal](https://github.com/datafuselabs/opendal#services) 支持的其他存储服务
* 由 [Apache OpenDAL](https://github.com/datafuselabs/opendal#services) 支持的其他存储服务

:::info 高级用户

Expand Down Expand Up @@ -588,4 +588,4 @@ SELECT count(*) FROM t1;

- [管理设置](/sql/sql-reference/manage-settings)：根据你的需求优化Databend。
- [加载与卸载数据](/guides/load-data)：管理Databend中的数据导入/导出。
- [可视化](/guides/visualize)：将Databend与可视化工具集成，以获得洞察力。
- [可视化](/guides/visualize)：将Databend与可视化工具集成，以获得洞察力。
2 changes: 1 addition & 1 deletion docs/guides/00-overview/02-community/01-rfcs/20220704-presign.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ MySQL [(none)]> PRESIGN UPLOAD @my_stage/books.csv

`PRESIGN` will be implemented as a statement instead of a function so that we can return the HTTP method, headers, and URL at the same time.

Most jobs have been done via [OpenDAL presign](https://opendal.databend.rs/rfcs/0413-presign.html).
Most jobs have been done via [Apache OpenDAL presign](https://opendal.databend.rs/rfcs/0413-presign.html).

The syntax will be:

Expand Down
4 changes: 2 additions & 2 deletions docs/guides/00-overview/02-community/01-rfcs/20220725-cache.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -94,7 +94,7 @@ As discussed before, developers now have three kinds of `Operator` to handle dif

### Cache Operator

`Cache Operator` will be implemented as an [OpenDAL Layer](https://docs.rs/opendal/0.11.2/opendal/trait.Layer.html):
`Cache Operator` will be implemented as an [Apache OpenDAL Layer](https://docs.rs/opendal/0.11.2/opendal/trait.Layer.html):

```rust
#[derive(Clone, Default, Debug)]
Expand Down Expand Up @@ -149,4 +149,4 @@ None.

### OpenCache

[OpenCache](https://github.com/datafuselabs/opencache) is an ongoing work from databend community to build a distributed cache services. OpenDAL will implement native support for `OpenCache` once its API is stable. After that, users can deploy and use OpenCache as `cache` storage.
[OpenCache](https://github.com/datafuselabs/opencache) is an ongoing work from databend community to build a distributed cache services. Apache OpenDAL will implement native support for `OpenCache` once its API is stable. After that, users can deploy and use OpenCache as `cache` storage.
6 changes: 3 additions & 3 deletions docs/guides/10-deploy/11-cluster/11-deploying-databend-on-kubernetes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ import TabItem from '@theme/TabItem';
* Create a Cloud Object Storage with corresponding credentials, i.e., `access_key_id` and `secret_access_key`.
* AWS S3 or other S3 compatible storage service
* Azure Storage Blob
* Other storage services supported by [opendal](https://github.com/datafuselabs/opendal#services)
* Other storage services supported by [Apache OpenDAL](https://github.com/datafuselabs/opendal#services)

:::info For advanced user

Expand Down Expand Up @@ -589,6 +589,6 @@ Note the `serviceMonitor` should be enabled when deploying meta and query cluste

After deploying Databend, you might need to learn about the following topics:

- [Manage Settings](/sql/sql-reference/manage-settings): Optimize Databend for your needs.
- [Manage Settings](/sql/sql-reference/manage-settings): Optimize Databend for your needs.
- [Load & Unload Data](/guides/load-data): Manage data import/export in Databend.
- [Visualize](/guides/visualize): Integrate Databend with visualization tools for insights.
- [Visualize](/guides/visualize): Integrate Databend with visualization tools for insights.