Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
6 changes: 1 addition & 5 deletions TOC-tidb-cloud-starter.md
Original file line number Diff line number Diff line change
Expand Up @@ -135,15 +135,11 @@
- [排查从 Amazon S3 导入数据期间的访问被拒绝错误](/tidb-cloud/troubleshoot-import-access-denied-error.md)
- [将 AWS DMS 连接到 TiDB Cloud](/tidb-cloud/tidb-cloud-connect-aws-dms.md)
- 探索数据
- [SQL 编辑器中的 Chat2Query](/tidb-cloud/explore-data-with-chat2query.md) ![PREVIEW](/media/tidb-cloud/blank_transparent_placeholder.png)
- [SQL 编辑器](/tidb-cloud/explore-data-with-sql-editor.md) ![PREVIEW](/media/tidb-cloud/blank_transparent_placeholder.png)
- [SQL 代理账户](/tidb-cloud/sql-proxy-account.md)
- 数据服务 ![PREVIEW](/media/tidb-cloud/blank_transparent_placeholder.png)
- [概述](/tidb-cloud/data-service-overview.md)
- [快速上手](/tidb-cloud/data-service-get-started.md)
- Chat2Query API
- [快速上手](/tidb-cloud/use-chat2query-api.md)
- [启动多轮 Chat2Query](/tidb-cloud/use-chat2query-sessions.md)
- [使用知识库](/tidb-cloud/use-chat2query-knowledge.md)
- [管理数据应用](/tidb-cloud/data-service-manage-data-app.md)
- [管理端点](/tidb-cloud/data-service-manage-endpoint.md)
- [API 密钥](/tidb-cloud/data-service-api-key.md)
Expand Down
6 changes: 1 addition & 5 deletions TOC-tidb-cloud.md
Original file line number Diff line number Diff line change
Expand Up @@ -171,15 +171,11 @@
- [数据迁移的预检查错误、迁移错误和警报](/tidb-cloud/tidb-cloud-dm-precheck-and-troubleshooting.md)
- [将 AWS DMS 连接到 TiDB Cloud](/tidb-cloud/tidb-cloud-connect-aws-dms.md)
- 探索数据
- [SQL 编辑器中的 Chat2Query](/tidb-cloud/explore-data-with-chat2query.md) ![PREVIEW](/media/tidb-cloud/blank_transparent_placeholder.png)
- [SQL 编辑器](/tidb-cloud/explore-data-with-sql-editor.md) ![PREVIEW](/media/tidb-cloud/blank_transparent_placeholder.png)
- [SQL 代理账户](/tidb-cloud/sql-proxy-account.md)
- 数据服务 ![PREVIEW](/media/tidb-cloud/blank_transparent_placeholder.png)
- [概述](/tidb-cloud/data-service-overview.md)
- [快速上手](/tidb-cloud/data-service-get-started.md)
- Chat2Query API
- [快速上手](/tidb-cloud/use-chat2query-api.md)
- [启动多轮 Chat2Query](/tidb-cloud/use-chat2query-sessions.md)
- [使用知识库](/tidb-cloud/use-chat2query-knowledge.md)
- [管理数据应用](/tidb-cloud/data-service-manage-data-app.md)
- [管理端点](/tidb-cloud/data-service-manage-endpoint.md)
- [API 密钥](/tidb-cloud/data-service-api-key.md)
Expand Down
2 changes: 1 addition & 1 deletion latest_translation_commit.json
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
{
"target": "release-8.5",
"sha": "212f51701c89f5ffe0a030e70a5ff32466af7646"
"sha": "d96fa6c87cc4d3710639c4245fb7528584dffffa"
}
124 changes: 124 additions & 0 deletions sql-statements/sql-statement-add-index.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,7 @@
| 'INVISIBLE'
| 'GLOBAL'
| 'LOCAL'
| 'WHERE' Expression

IndexType
::= 'BTREE'
Expand Down Expand Up @@ -92,6 +93,129 @@
2 rows in set (0.00 sec)
```

## 部分索引

> **注意:**
>
> TiDB Self-Managed 和 TiDB Cloud Dedicated 从 v8.5.7 开始支持部分索引,TiDB Cloud Essential 和 Premium 从 CLOUD.202603.1 开始支持部分索引。

部分索引是建立在表中部分行上的索引。添加部分索引时,你可以指定一个条件表达式(也称为谓词)来定义这部分行。索引仅包含满足该谓词的行的条目。

Check failure on line 102 in sql-statements/sql-statement-add-index.md

View workflow job for this annotation

GitHub Actions / vale

[vale] reported by reviewdog 🐶 [PingCAP.ZhPunctuation] Don't use Chinese punctuation (。) in English text. Raw Output: {"message":"[PingCAP.ZhPunctuation] Don't use Chinese punctuation (。) in English text.","location":{"path":"sql-statements/sql-statement-add-index.md","range":{"start":{"line":102,"column":205},"end":{"line":102,"column":208}}},"severity":"ERROR","code":{"value":"PingCAP.ZhPunctuation"}}

Check failure on line 102 in sql-statements/sql-statement-add-index.md

View workflow job for this annotation

GitHub Actions / vale

[vale] reported by reviewdog 🐶 [PingCAP.ZhPunctuation] Don't use Chinese punctuation (。) in English text. Raw Output: {"message":"[PingCAP.ZhPunctuation] Don't use Chinese punctuation (。) in English text.","location":{"path":"sql-statements/sql-statement-add-index.md","range":{"start":{"line":102,"column":157},"end":{"line":102,"column":160}}},"severity":"ERROR","code":{"value":"PingCAP.ZhPunctuation"}}

Check failure on line 102 in sql-statements/sql-statement-add-index.md

View workflow job for this annotation

GitHub Actions / vale

[vale] reported by reviewdog 🐶 [PingCAP.ZhPunctuation] Don't use Chinese punctuation (,) in English text. Raw Output: {"message":"[PingCAP.ZhPunctuation] Don't use Chinese punctuation (,) in English text.","location":{"path":"sql-statements/sql-statement-add-index.md","range":{"start":{"line":102,"column":76},"end":{"line":102,"column":79}}},"severity":"ERROR","code":{"value":"PingCAP.ZhPunctuation"}}

Check failure on line 102 in sql-statements/sql-statement-add-index.md

View workflow job for this annotation

GitHub Actions / vale

[vale] reported by reviewdog 🐶 [PingCAP.ZhPunctuation] Don't use Chinese punctuation (。) in English text. Raw Output: {"message":"[PingCAP.ZhPunctuation] Don't use Chinese punctuation (。) in English text.","location":{"path":"sql-statements/sql-statement-add-index.md","range":{"start":{"line":102,"column":52},"end":{"line":102,"column":55}}},"severity":"ERROR","code":{"value":"PingCAP.ZhPunctuation"}}

### 使用场景

在以下场景中,使用部分索引有助于提升查询性能或减少索引维护开销:

Check failure on line 106 in sql-statements/sql-statement-add-index.md

View workflow job for this annotation

GitHub Actions / vale

[vale] reported by reviewdog 🐶 [PingCAP.ZhPunctuation] Don't use Chinese punctuation (:) in English text. Raw Output: {"message":"[PingCAP.ZhPunctuation] Don't use Chinese punctuation (:) in English text.","location":{"path":"sql-statements/sql-statement-add-index.md","range":{"start":{"line":106,"column":94},"end":{"line":106,"column":97}}},"severity":"ERROR","code":{"value":"PingCAP.ZhPunctuation"}}

Check failure on line 106 in sql-statements/sql-statement-add-index.md

View workflow job for this annotation

GitHub Actions / vale

[vale] reported by reviewdog 🐶 [PingCAP.ZhPunctuation] Don't use Chinese punctuation (,) in English text. Raw Output: {"message":"[PingCAP.ZhPunctuation] Don't use Chinese punctuation (,) in English text.","location":{"path":"sql-statements/sql-statement-add-index.md","range":{"start":{"line":106,"column":19},"end":{"line":106,"column":22}}},"severity":"ERROR","code":{"value":"PingCAP.ZhPunctuation"}}

- **选择性过滤**:当你经常基于特定条件查询一小部分行时,可以使用部分索引。对于满足部分索引谓词的查询,TiDB 可以使用部分索引来避免扫描无关行,并减少索引占用的存储空间。

Check failure on line 108 in sql-statements/sql-statement-add-index.md

View workflow job for this annotation

GitHub Actions / vale

[vale] reported by reviewdog 🐶 [PingCAP.ZhPunctuation] Don't use Chinese punctuation (。) in English text. Raw Output: {"message":"[PingCAP.ZhPunctuation] Don't use Chinese punctuation (。) in English text.","location":{"path":"sql-statements/sql-statement-add-index.md","range":{"start":{"line":108,"column":106},"end":{"line":108,"column":109}}},"severity":"ERROR","code":{"value":"PingCAP.ZhPunctuation"}}

Check failure on line 108 in sql-statements/sql-statement-add-index.md

View workflow job for this annotation

GitHub Actions / vale

[vale] reported by reviewdog 🐶 [PingCAP.ZhPunctuation] Don't use Chinese punctuation (,) in English text. Raw Output: {"message":"[PingCAP.ZhPunctuation] Don't use Chinese punctuation (,) in English text.","location":{"path":"sql-statements/sql-statement-add-index.md","range":{"start":{"line":108,"column":79},"end":{"line":108,"column":82}}},"severity":"ERROR","code":{"value":"PingCAP.ZhPunctuation"}}

Check failure on line 108 in sql-statements/sql-statement-add-index.md

View workflow job for this annotation

GitHub Actions / vale

[vale] reported by reviewdog 🐶 [PingCAP.ZhPunctuation] Don't use Chinese punctuation (:) in English text. Raw Output: {"message":"[PingCAP.ZhPunctuation] Don't use Chinese punctuation (:) in English text.","location":{"path":"sql-statements/sql-statement-add-index.md","range":{"start":{"line":108,"column":22},"end":{"line":108,"column":25}}},"severity":"ERROR","code":{"value":"PingCAP.ZhPunctuation"}}
- **条件唯一性**:当你只需要对满足特定条件的行强制执行唯一性约束时,可以使用唯一部分索引,以避免将唯一性约束应用到整张表。
- **降低 DML 开销**:当大量 `INSERT`、`UPDATE` 或 `DELETE` 操作影响到不需要建立索引的行时,可以使用部分索引。与维护完整索引相比,维护部分索引可以减少索引维护开销。

### 添加部分索引

你可以通过在索引定义后追加 `WHERE` 子句来添加部分索引。例如:

```sql
CREATE TABLE t1 (c1 INT, c2 INT, c3 TEXT);
ALTER TABLE t1 ADD INDEX idx1 (c1) WHERE c2 > 10;
```

你还可以添加唯一部分索引:

```sql
ALTER TABLE t1 ADD UNIQUE INDEX idx2 (c1, c2) WHERE c3 = 'abc';
```

### 使用示例

以下示例演示了如何有效使用部分索引。

创建一个包含用户数据的表:

```sql
CREATE TABLE users (
id INT PRIMARY KEY AUTO_INCREMENT,
name VARCHAR(100),
status VARCHAR(20),
created_at DATETIME,
score INT
);
```

为常见查询模式添加部分索引:

```sql
ALTER TABLE users ADD INDEX idx_active_users (name) WHERE status = 'active';
ALTER TABLE users ADD INDEX idx_high_score_users (created_at) WHERE score > 1000;
ALTER TABLE users ADD INDEX idx_pending_status (status) WHERE status = 'pending';
```

然后,以下查询可以使用部分索引:

```sql
mysql> EXPLAIN SELECT * FROM users WHERE status = 'active' AND name = 'John';
+-------------------------------+---------+-----------+-------------------------------------------+-------------------------------------------------------+
| id | estRows | task | access object | operator info |
+-------------------------------+---------+-----------+-------------------------------------------+-------------------------------------------------------+
| IndexLookUp_9 | 1.00 | root | | |
| ├─IndexRangeScan_6(Build) | 10.00 | cop[tikv] | table:users, index:idx_active_users(name) | range:["John","John"], keep order:false, stats:pseudo |
| └─Selection_8(Probe) | 1.00 | cop[tikv] | | eq(test.users.status, "active") |
| └─TableRowIDScan_7 | 10.00 | cop[tikv] | table:users | keep order:false, stats:pseudo |
+-------------------------------+---------+-----------+-------------------------------------------+-------------------------------------------------------+
4 rows in set (0.00 sec)

mysql> EXPLAIN SELECT * FROM users WHERE status = 'active' ORDER BY name;
+-------------------------------+----------+-----------+-------------------------------------------+---------------------------------+
| id | estRows | task | access object | operator info |
+-------------------------------+----------+-----------+-------------------------------------------+---------------------------------+
| IndexLookUp_18 | 10.00 | root | | |
| ├─IndexFullScan_15(Build) | 10000.00 | cop[tikv] | table:users, index:idx_active_users(name) | keep order:true, stats:pseudo |
| └─Selection_17(Probe) | 10.00 | cop[tikv] | | eq(test.users.status, "active") |
| └─TableRowIDScan_16 | 10000.00 | cop[tikv] | table:users | keep order:false, stats:pseudo |
+-------------------------------+----------+-----------+-------------------------------------------+---------------------------------+
4 rows in set (0.00 sec)

mysql> EXPLAIN SELECT * FROM users WHERE score > 10000 ORDER BY created_at;
+-------------------------------+----------+-----------+-----------------------------------------------------+--------------------------------+
| id | estRows | task | access object | operator info |
+-------------------------------+----------+-----------+-----------------------------------------------------+--------------------------------+
| IndexLookUp_18 | 3333.33 | root | | |
| ├─IndexFullScan_15(Build) | 10000.00 | cop[tikv] | table:users, index:idx_high_score_users(created_at) | keep order:true, stats:pseudo |
| └─Selection_17(Probe) | 3333.33 | cop[tikv] | | gt(test.users.score, 10000) |
| └─TableRowIDScan_16 | 10000.00 | cop[tikv] | table:users | keep order:false, stats:pseudo |
+-------------------------------+----------+-----------+-----------------------------------------------------+--------------------------------+
4 rows in set (0.00 sec)

mysql> EXPLAIN SELECT * FROM users WHERE status = 'pending';
+-------------------------------+---------+-----------+-----------------------------------------------+-------------------------------------------------------------+
| id | estRows | task | access object | operator info |
+-------------------------------+---------+-----------+-----------------------------------------------+-------------------------------------------------------------+
| IndexLookUp_7 | 10.00 | root | | |
| ├─IndexRangeScan_5(Build) | 10.00 | cop[tikv] | table:users, index:idx_pending_status(status) | range:["pending","pending"], keep order:false, stats:pseudo |
| └─TableRowIDScan_6(Probe) | 10.00 | cop[tikv] | table:users | keep order:false, stats:pseudo |
+-------------------------------+---------+-----------+-----------------------------------------------+-------------------------------------------------------------+
3 rows in set (0.00 sec)
```

如果查询的谓词不满足部分索引定义的条件,TiDB 不会选择该部分索引,即使使用了 hint 也是如此。例如,以下语句无法使用部分索引 `idx_high_score_users`,因为查询谓词 `score > 100` 不满足部分索引定义 `score > 1000`:

```sql
mysql> EXPLAIN SELECT * FROM users USE INDEX(idx_high_score_users) WHERE score > 100 ORDER BY created_at;
+---------------------------+----------+-----------+---------------+--------------------------------+
| id | estRows | task | access object | operator info |
+---------------------------+----------+-----------+---------------+--------------------------------+
| Sort_5 | 3333.33 | root | | test.users.created_at |
| └─TableReader_10 | 3333.33 | root | | data:Selection_9 |
| └─Selection_9 | 3333.33 | cop[tikv] | | gt(test.users.score, 100) |
| └─TableFullScan_8 | 10000.00 | cop[tikv] | table:users | keep order:false, stats:pseudo |
+---------------------------+----------+-----------+---------------+--------------------------------+
```

### 限制

- 部分索引中的 `WHERE` 子句支持基本比较运算符(`=`、`!=`、`<`、`<=`、`>`、`>=`)、`IS NULL`、`IS NOT NULL` 以及带常量值的 `IN` 谓词。
- 谓词中的列和常量值必须具有相同的数据类型。
- 谓词只能引用同一张表中的列。
- 不能在表达式索引上创建部分索引。

## MySQL 兼容性

* TiDB 在语法上接受 `HASH`、`BTREE` 和 `RTREE` 等索引类型以兼容 MySQL,但会忽略这些类型。
Expand Down
4 changes: 3 additions & 1 deletion sql-statements/sql-statement-create-index.md
Original file line number Diff line number Diff line change
Expand Up @@ -368,7 +368,9 @@ Query OK, 1 row affected (0.00 sec)

## 部分索引 {#partial-indexes}

<span class="version-mark">TiDB Self-Managed 和 TiDB Cloud Dedicated 从 v8.5.7 版本开始引入,TiDB Cloud Essential 和 Premium 从 CLOUD.202603.1 开始引入</span>
> **注意:**
>
> TiDB Self-Managed 和 TiDB Cloud Dedicated 从 v8.5.7 开始支持部分索引,TiDB Cloud Essential 和 Premium 从 CLOUD.202603.1 开始支持部分索引。

部分索引是建立在表中部分行子集上的索引。创建部分索引时,你可以指定一个条件表达式,也称为谓词,用于定义这个行子集。索引中仅包含满足该谓词的行的条目。

Expand Down
40 changes: 40 additions & 0 deletions system-variables.md
Original file line number Diff line number Diff line change
Expand Up @@ -6270,6 +6270,26 @@ Query OK, 0 rows affected, 1 warning (0.00 sec)

</CustomContent>

<CustomContent platform="tidb-cloud">

### tidb_stmt_summary_group_by_user <span class="version-mark">在 CLOUD.202603.1 中引入</span> {#tidb_stmt_summary_group_by_user}

> **Note:**
>
> - 对于 TiDB Cloud Starter,此变量不受支持。
> - 对于 TiDB Cloud Essential 和 Premium,此变量为只读。

- Scope: GLOBAL
- Persists to cluster: Yes
- 是否受 Hint [SET_VAR](/optimizer-hints.md#set_varvar_namevar_value) 控制: No
- Type: Boolean
- Default value: TiDB Cloud Essential 和 TiDB Cloud Premium 为 `ON`
- 此变量控制是否将执行 SQL 语句的用户作为 [statement summary tables](/statement-summary-tables.md) 中的聚合维度之一。当此变量设置为 `OFF` 时,TiDB 会将不同用户执行的相同 SQL digest 聚合到同一行中,`SAMPLE_USER` 字段显示一个采样用户。当此变量设置为 `ON` 时,TiDB 会将不同用户执行的相同 SQL digest 分别聚合到不同的行中,每一行的 `SAMPLE_USER` 字段表示执行该语句的用户。
- 修改此变量会清除当前内存中的 statement summary 数据,因为修改前后的数据使用了不同的维度进行聚合。这不会影响持久化到磁盘的历史数据。
- 启用此变量后,statement summary 记录数可能会随着同一 SQL digest 的不同执行用户数量增加而增加,从而增加内存使用量。

</CustomContent>

### tidb_stmt_summary_history_size <span class="version-mark">从 v4.0 版本开始引入</span>

> **注意:**
Expand Down Expand Up @@ -6345,6 +6365,26 @@ Query OK, 0 rows affected, 1 warning (0.00 sec)

</CustomContent>

<CustomContent platform="tidb-cloud">

### tidb_stmt_summary_persist_evicted <span class="version-mark">在 CLOUD.202603.1 中引入</span> {#tidb_stmt_summary_persist_evicted}

> **Note:**
>
> - 对于 TiDB Cloud Starter,此变量不受支持。
> - 对于 TiDB Cloud Essential 和 Premium,此变量为只读。

- Scope: GLOBAL
- Persists to cluster: Yes
- 是否受 Hint [SET_VAR](/optimizer-hints.md#set_varvar_namevar_value) 控制: No
- Type: Boolean
- Default value: `OFF`
- 此变量控制在启用[语句摘要持久化](/statement-summary-tables.md#persist-statements-summary)后,是否将被 LRU 淘汰的 statement summary 记录写入 statement summary 日志。TiDB 会将这些 JSON 记录标记为 `"evicted": true`,以便下游日志消费者识别它们。
- 此变量仅在启用 [tidb_stmt_summary_enable_persistent](/system-variables.md#tidb_stmt_summary_enable_persistent-new-in-v660) 时生效。TiDB 不会将标记为 `"evicted": true` 的记录作为 `statements_summary_history` 或 `cluster_statements_summary_history` 的查询结果返回。
- 启用此变量后,随着 LRU 淘汰变得更频繁,日志量会增加。TiDB 使用异步缓冲机制写入被淘汰的记录。当缓冲队列已满时,TiDB 可能会丢弃新的被淘汰记录。

</CustomContent>

### tidb_stmt_summary_refresh_interval <span class="version-mark">从 v4.0 版本开始引入</span>

> **注意:**
Expand Down
10 changes: 10 additions & 0 deletions tidb-cloud-lake/guides/data-lineage.md
Original file line number Diff line number Diff line change
Expand Up @@ -105,6 +105,16 @@ REFRESH LINEAGE FOR ALL VIEWS;

刷新操作会为 `default` catalog 中的所有视图校正血缘信息。它只会报告需要变更或无法处理的视图;未发生变化的视图不会显示。该命令需要全局 `SUPER` 权限。有关输出详情,请参见 [`REFRESH LINEAGE`](/tidb-cloud-lake/sql/refresh-lineage.md)。

## 导出到 OpenMetadata {#export-to-openmetadata}

要在 [OpenMetadata](https://open-metadata.org) 中查看 {{{ .lake }}} 血缘,请使用 [lake-openmetadata-ingestion](https://github.com/tidbcloud/lake-openmetadata-ingestion)。该工具通过 REST API 将 {{{ .lake }}} 中的元信息(数据库、表、视图和列)和血缘(表级别和列级别)推送到 OpenMetadata。有关安装、配置和使用方法,请参阅该项目的 [README](https://github.com/tidbcloud/lake-openmetadata-ingestion)。

> **注意:**
>
> - 该工具当前仅支持元信息和血缘导入。
> - 对于初始同步,请先运行 `lake-om -c config.yaml metadata` 直至完成,然后运行 `lake-om -c config.yaml lineage --full`。如果某条血缘边的任一端点在 OpenMetadata 中尚不存在,则会跳过该血缘边。
> - 对于持续同步,请调度 cron 或 Airflow 工作流,先运行 `lake-om -c config.yaml metadata` 直至完成,再运行 `lake-om -c config.yaml lineage`。长时间中断后,请运行 `lake-om -c config.yaml lineage --full`。

## 限制 {#limitations}

- `GET_LINEAGE` 最多只能遍历五跳。
Expand Down
8 changes: 1 addition & 7 deletions tidb-cloud/ai-feature-concepts.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,16 +5,10 @@ summary: 了解 TiDB Cloud 的 AI 功能。

# AI 功能

TiDB Cloud 的 AI 功能使你能够充分利用先进技术进行数据探索、搜索和集成。从基于自然语言驱动的 SQL 查询生成,到高性能向量搜索,TiDB 将数据库能力与现代 AI 功能相结合,为创新应用提供动力。TiDB 支持主流 AI 框架、embedding 模型,并可与 ORM 库无缝集成,为语义搜索和 AI 驱动分析等场景提供了多样化的平台。
TiDB Cloud 的 AI 功能使你能够充分利用先进技术进行数据探索、搜索和集成。TiDB 将数据库能力与现代 AI 功能相结合,为创新应用提供动力。TiDB 支持主流 AI 框架、嵌入模型,并可与 ORM 库无缝集成,为语义搜索和 AI 驱动分析等场景提供了多样化的平台。

本文档将重点介绍这些 AI 功能及其如何提升 TiDB 体验。

## Chat2Query(PREVIEW) {#chat2query-preview}

Chat2Query 是集成在 SQL Editor 中的 AI 驱动功能,能够帮助用户通过自然语言指令生成、调试或重写 SQL 查询。更多信息,参见 [Explore your data with AI-assisted SQL Editor](/tidb-cloud/explore-data-with-chat2query.md)。

此外,TiDB Cloud 为 TiDB Cloud Starter 实例提供了 Chat2Query API。启用后,TiDB Cloud 会自动创建一个名为 Chat2Query 的系统 Data App,以及一个 Data Service 中的 Chat2Data endpoint。你可以调用该 endpoint,通过提供指令让 AI 生成并执行 SQL 语句。更多信息,参见 [Get started with Chat2Query API](/tidb-cloud/use-chat2query-api.md)。

## 向量搜索(PREVIEW) {#vector-search-preview}

向量搜索是一种以数据语义为优先级的搜索方法,能够返回更相关的结果。
Expand Down
6 changes: 6 additions & 0 deletions tidb-cloud/architecture-concepts.md
Original file line number Diff line number Diff line change
Expand Up @@ -134,6 +134,12 @@ TiDB Cloud Lake 在一个平台中支持 ANSI SQL、半结构化数据处理、

更多详情,请参见 [TiDB Cloud Lake Overview](https://docs.pingcap.com/tidbcloudlake/lake-overview/)。

## TiDB Cloud Filesystem {#tidb-cloud-filesystem}

TiDB Cloud Filesystem 提供持久、共享的文件存储,独立于访问它的机器和进程。你可以使用 `ti fs` 命令访问文件,或将文件系统挂载为本地目录,而无需预配或管理 TiDB 数据库。

更多详细信息,请参见 [TiDB Cloud Filesystem](https://docs.pingcap.com/tidbcloud-filesystem/filesystem-intro/)。

## TiDB Cloud 控制台

[TiDB Cloud 控制台](https://tidbcloud.com/) 是 TiDB Cloud 资源的基于 Web 的管理界面。你可以通过该平台管理 TiDB Cloud 资源、导入或迁移数据、监控性能指标、配置备份、设置安全控制,并与其他云服务集成,所有操作均可在一个用户友好的平台上完成。
Expand Down
Loading
Loading