This is an automated email from the ASF dual-hosted git repository.
eldenmoon pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris-website.git
The following commit(s) were added to refs/heads/master by this push:
new 5f7f0324260 [doc](load) Remove Native file format docs (#4139)
5f7f0324260 is described below
commit 5f7f0324260157088260ed32178c7109166465c1
Author: lihangyu <[email protected]>
AuthorDate: Tue Sep 15 15:02:43 2026 +0800
[doc](load) Remove Native file format docs (#4139)
## Versions
- [x] dev
- [x] 4.x
- [ ] 3.x
- [ ] 2.1
## Languages
- [x] Chinese
- [x] English
## Docs Checklist
- [x] Checked by AI
- [ ] Test Cases Built
## Summary
The Doris Native file format is being removed from Apache Doris, so this
PR removes its load documentation from both the dev and version-4.x
docs:
- `docs/data-operate/import/file-format/native.md` and
`versioned_docs/version-4.x/data-operate/import/file-format/native.md`
(English)
-
`i18n/zh-CN/docusaurus-plugin-content-docs/{current,version-4.x}/data-operate/import/file-format/native.md`
(Chinese)
- the `data-operate/import/file-format/native` entry in `sidebars.ts`
and `versioned_sidebars/version-4.x-sidebars.json`
Related doc PR that added these pages: #3190
Related Doris PR: https://github.com/apache/doris/pull/67993
🤖 Generated with [Claude Code](https://claude.com/claude-code)
---------
Co-authored-by: Claude Opus 5 <[email protected]>
---
docs/data-operate/import/file-format/native.md | 120 ---------------------
.../data-operate/import/file-format/native.md | 120 ---------------------
.../data-operate/import/file-format/native.md | 120 ---------------------
sidebars.ts | 1 -
.../data-operate/import/file-format/native.md | 120 ---------------------
versioned_sidebars/version-4.x-sidebars.json | 3 +-
6 files changed, 1 insertion(+), 483 deletions(-)
diff --git a/docs/data-operate/import/file-format/native.md
b/docs/data-operate/import/file-format/native.md
deleted file mode 100644
index f27821bf5fa..00000000000
--- a/docs/data-operate/import/file-format/native.md
+++ /dev/null
@@ -1,120 +0,0 @@
----
-{
- "title": "Native",
- "language": "en",
- "description": "How to load Native format data in Apache Doris, suitable
for Doris internal data exchange and backup scenarios, providing the highest
load efficiency.",
- "keywords": [
- "Doris Native format",
- "Native load",
- "Stream Load Native",
- "Broker Load Native",
- "Doris internal data exchange",
- "Doris backup format"
- ]
-}
----
-
-<!-- Knowledge type: Procedure -->
-<!-- Applicable scenarios: Doris internal data flow / Backup and restore -->
-
-This document describes how to load **Native** format data files in Apache
Doris. Native is a binary data format dedicated to Doris, suitable as an
**internal data exchange and backup format** rather than a general-purpose file
exchange format. When data flows only within Doris, prefer the Native format to
achieve the highest load efficiency.
-
-> This feature is supported since version 4.1.0.
-
-## Applicable Scenarios
-
-The Native format mainly targets the following scenarios:
-
-- **Data migration between Doris clusters**: Efficiently transfer data between
different Doris clusters.
-- **Data backup and restore**: Export Doris table data to Native files for
archival, then load them back when needed.
-- **Bulk data exchange**: Move large volumes of data with the highest
efficiency within Doris internal pipelines.
-
-> Tip: If you need to exchange data with external systems, use general-purpose
formats such as CSV, JSON, Parquet, or ORC instead of Native.
-
-## Supported Load Methods
-
-The following table lists the load methods that support the Native format and
their typical uses:
-
-| Load Method | Typical Use | Documentation Link |
-| --- | --- | --- |
-| Stream Load | Push local Native files over HTTP | [Stream
Load](../import-way/stream-load-manual.md) |
-| Broker Load | Asynchronously load Native files from object storage / HDFS |
[Broker Load](../import-way/broker-load-manual.md) |
-| INSERT INTO FROM S3 TVF | Read Native files directly from S3 via SQL | [S3
TVF](../../../sql-manual/sql-functions/table-valued-functions/s3) |
-| INSERT INTO FROM HDFS TVF | Read Native files directly from HDFS via SQL |
[HDFS TVF](../../../sql-manual/sql-functions/table-valued-functions/hdfs) |
-
-## Usage Examples
-
-The following examples show how to use the Native format with different load
methods. Choose the appropriate method based on the data source (local file /
object storage / HDFS) and load mode (synchronous / asynchronous).
-
-### Load Local Native Files via Stream Load
-
-Applicable scenario: A Native file resides on the local machine or on a server
that can access the FE HTTP port, and you need a fast synchronous load.
-
-Steps:
-
-1. Prepare the Native file `example.native`.
-2. Use `curl` to push the file through the Stream Load interface, and specify
the format with the request header `format: native`.
-
-```shell
-curl --location-trusted -u <user>:<passwd> \
- -H "format: native" \
- -T example.native \
- http://<fe_host>:<fe_http_port>/api/example_db/example_table/_stream_load
-```
-
-### Load from Object Storage via Broker Load
-
-Applicable scenario: The Native file is stored in remote storage such as S3
(or an S3-compatible object store), and you need an asynchronous batch load.
-
-Key points:
-
-- Specify the Native file path in `DATA INFILE`.
-- Explicitly declare the format with `FORMAT AS "native"`.
-- Provide the authentication and connection information required to access the
object storage in `WITH S3`.
-
-```sql
-LOAD LABEL example_db.example_label
-(
- DATA INFILE("s3://bucket/example.native")
- INTO TABLE example_table
- FORMAT AS "native"
-)
-WITH S3
-(
- ...
-);
-```
-
-### Load via INSERT INTO with TVF
-
-Applicable scenario: You want to read remote Native files directly with SQL
and write them into a target table, making it easy to combine with query,
filter, and transformation logic.
-
-Key points:
-
-- Specify `uri` and `format = "native"` in the TVF parameters.
-- Use `INSERT INTO ... SELECT` to write the read result into the target table.
-
-```sql
-INSERT INTO example_table
-SELECT *
-FROM S3
-(
- "uri" = "s3://bucket/example.native",
- "format" = "native",
- ...
-);
-```
-
-## FAQ
-
-**Q1: Can the Native format be used to exchange data with external systems?**
-
-Not recommended. Native is a binary format dedicated to Doris and is not
compatible with external systems. For cross-system data exchange, prefer
general-purpose formats such as CSV, JSON, Parquet, or ORC.
-
-**Q2: Why is the Native format recommended for data flow within Doris?**
-
-The Native format aligns with Doris internal data structures, so serialization
and deserialization overhead is minimal. As a result, it delivers the highest
load efficiency between Doris clusters or in backup scenarios.
-
-**Q3: Which load methods support the Native format?**
-
-Stream Load, Broker Load, and `INSERT INTO ... FROM S3 / HDFS` TVF are
currently supported. See the "Supported Load Methods" section above for details.
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/file-format/native.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/file-format/native.md
deleted file mode 100644
index 651b2421add..00000000000
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/file-format/native.md
+++ /dev/null
@@ -1,120 +0,0 @@
----
-{
- "title": "Native",
- "language": "zh-CN",
- "description": "如何在 Apache Doris 中导入 Native 格式数据，适用于 Doris
内部数据交换与备份场景，提供最高导入效率。",
- "keywords": [
- "Doris Native 格式",
- "Native 导入",
- "Stream Load Native",
- "Broker Load Native",
- "Doris 内部数据交换",
- "Doris 备份格式"
- ]
-}
----
-
-<!-- 知识类型: 操作步骤 -->
-<!-- 适用场景: Doris 内部数据流转 / 备份恢复 -->
-
-本文介绍如何在 Apache Doris 中导入 **Native** 格式的数据文件。Native 是 Doris 专用的二进制数据格式，适合作为
**内部数据交换与备份格式**，而非通用文件交换格式。当数据仅在 Doris 内部流转时，应优先选择 Native 格式以获得最高的导入效率。
-
-> 该功能自 4.1.0 版本支持。
-
-## 适用场景
-
-Native 格式主要面向以下场景：
-
-- **Doris 集群间数据迁移**：在不同 Doris 集群间高效传输数据。
-- **数据备份与恢复**：将 Doris 表数据导出为 Native 文件后归档保存，需要时再导入。
-- **批量数据交换**：在 Doris 内部链路中以最高效率搬运大批量数据。
-
-> 提示：如果需要与外部系统交换数据，请使用 CSV、JSON、Parquet、ORC 等通用格式，而非 Native。
-
-## 支持的导入方式
-
-下表列出了支持 Native 格式的导入方式及其典型用途：
-
-| 导入方式 | 典型用途 | 文档链接 |
-| --- | --- | --- |
-| Stream Load | 通过 HTTP 推送本地 Native 文件 | [Stream
Load](../import-way/stream-load-manual.md) |
-| Broker Load | 从对象存储 / HDFS 异步加载 Native 文件 | [Broker
Load](../import-way/broker-load-manual.md) |
-| INSERT INTO FROM S3 TVF | 通过 SQL 从 S3 直接读取 Native 文件 | [S3
TVF](../../../sql-manual/sql-functions/table-valued-functions/s3) |
-| INSERT INTO FROM HDFS TVF | 通过 SQL 从 HDFS 直接读取 Native 文件 | [HDFS
TVF](../../../sql-manual/sql-functions/table-valued-functions/hdfs) |
-
-## 使用示例
-
-以下示例展示了不同导入方式下 Native 格式的使用方法。请根据数据来源（本地文件 / 对象存储 / HDFS）以及导入模式（同步 /
异步）选择合适的方式。
-
-### 通过 Stream Load 导入本地 Native 文件
-
-适用场景：本地或可访问 FE HTTP 端口的服务器上有 Native 文件，需要快速同步导入。
-
-操作步骤：
-
-1. 准备 Native 文件 `example.native`。
-2. 使用 `curl` 通过 Stream Load 接口推送，并通过请求头 `format: native` 指定格式。
-
-```shell
-curl --location-trusted -u <user>:<passwd> \
- -H "format: native" \
- -T example.native \
- http://<fe_host>:<fe_http_port>/api/example_db/example_table/_stream_load
-```
-
-### 通过 Broker Load 从对象存储导入
-
-适用场景：Native 文件存放在 S3（或兼容对象存储）等远端存储，需要异步批量导入。
-
-操作要点：
-
-- 在 `DATA INFILE` 中指定 Native 文件路径。
-- 使用 `FORMAT AS "native"` 显式声明格式。
-- 在 `WITH S3` 中补充访问对象存储所需的认证与连接信息。
-
-```sql
-LOAD LABEL example_db.example_label
-(
- DATA INFILE("s3://bucket/example.native")
- INTO TABLE example_table
- FORMAT AS "native"
-)
-WITH S3
-(
- ...
-);
-```
-
-### 通过 TVF 使用 INSERT INTO 导入
-
-适用场景：希望直接以 SQL 方式读取远端 Native 文件并写入目标表，便于与查询、过滤、转换等逻辑组合。
-
-操作要点：
-
-- 在 TVF 参数中指定 `uri` 与 `format = "native"`。
-- 通过 `INSERT INTO ... SELECT` 将读取结果写入目标表。
-
-```sql
-INSERT INTO example_table
-SELECT *
-FROM S3
-(
- "uri" = "s3://bucket/example.native",
- "format" = "native",
- ...
-);
-```
-
-## FAQ
-
-**Q1：Native 格式是否可以用于和外部系统交换数据？**
-
-不建议。Native 是 Doris 专用的二进制格式，与外部系统不兼容。跨系统的数据交换请优先选择 CSV、JSON、Parquet、ORC 等通用格式。
-
-**Q2：为什么在 Doris 内部流转数据时推荐使用 Native 格式？**
-
-Native 格式与 Doris 内部数据结构对齐，序列化与反序列化开销最小，因此在 Doris 集群之间或备份场景下能获得最高的导入效率。
-
-**Q3：哪些导入方式支持 Native 格式？**
-
-目前支持 Stream Load、Broker Load，以及 `INSERT INTO ... FROM S3 / HDFS` TVF
这几种方式，详见上文「支持的导入方式」章节。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/file-format/native.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/file-format/native.md
deleted file mode 100644
index 651b2421add..00000000000
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/file-format/native.md
+++ /dev/null
@@ -1,120 +0,0 @@
----
-{
- "title": "Native",
- "language": "zh-CN",
- "description": "如何在 Apache Doris 中导入 Native 格式数据，适用于 Doris
内部数据交换与备份场景，提供最高导入效率。",
- "keywords": [
- "Doris Native 格式",
- "Native 导入",
- "Stream Load Native",
- "Broker Load Native",
- "Doris 内部数据交换",
- "Doris 备份格式"
- ]
-}
----
-
-<!-- 知识类型: 操作步骤 -->
-<!-- 适用场景: Doris 内部数据流转 / 备份恢复 -->
-
-本文介绍如何在 Apache Doris 中导入 **Native** 格式的数据文件。Native 是 Doris 专用的二进制数据格式，适合作为
**内部数据交换与备份格式**，而非通用文件交换格式。当数据仅在 Doris 内部流转时，应优先选择 Native 格式以获得最高的导入效率。
-
-> 该功能自 4.1.0 版本支持。
-
-## 适用场景
-
-Native 格式主要面向以下场景：
-
-- **Doris 集群间数据迁移**：在不同 Doris 集群间高效传输数据。
-- **数据备份与恢复**：将 Doris 表数据导出为 Native 文件后归档保存，需要时再导入。
-- **批量数据交换**：在 Doris 内部链路中以最高效率搬运大批量数据。
-
-> 提示：如果需要与外部系统交换数据，请使用 CSV、JSON、Parquet、ORC 等通用格式，而非 Native。
-
-## 支持的导入方式
-
-下表列出了支持 Native 格式的导入方式及其典型用途：
-
-| 导入方式 | 典型用途 | 文档链接 |
-| --- | --- | --- |
-| Stream Load | 通过 HTTP 推送本地 Native 文件 | [Stream
Load](../import-way/stream-load-manual.md) |
-| Broker Load | 从对象存储 / HDFS 异步加载 Native 文件 | [Broker
Load](../import-way/broker-load-manual.md) |
-| INSERT INTO FROM S3 TVF | 通过 SQL 从 S3 直接读取 Native 文件 | [S3
TVF](../../../sql-manual/sql-functions/table-valued-functions/s3) |
-| INSERT INTO FROM HDFS TVF | 通过 SQL 从 HDFS 直接读取 Native 文件 | [HDFS
TVF](../../../sql-manual/sql-functions/table-valued-functions/hdfs) |
-
-## 使用示例
-
-以下示例展示了不同导入方式下 Native 格式的使用方法。请根据数据来源（本地文件 / 对象存储 / HDFS）以及导入模式（同步 /
异步）选择合适的方式。
-
-### 通过 Stream Load 导入本地 Native 文件
-
-适用场景：本地或可访问 FE HTTP 端口的服务器上有 Native 文件，需要快速同步导入。
-
-操作步骤：
-
-1. 准备 Native 文件 `example.native`。
-2. 使用 `curl` 通过 Stream Load 接口推送，并通过请求头 `format: native` 指定格式。
-
-```shell
-curl --location-trusted -u <user>:<passwd> \
- -H "format: native" \
- -T example.native \
- http://<fe_host>:<fe_http_port>/api/example_db/example_table/_stream_load
-```
-
-### 通过 Broker Load 从对象存储导入
-
-适用场景：Native 文件存放在 S3（或兼容对象存储）等远端存储，需要异步批量导入。
-
-操作要点：
-
-- 在 `DATA INFILE` 中指定 Native 文件路径。
-- 使用 `FORMAT AS "native"` 显式声明格式。
-- 在 `WITH S3` 中补充访问对象存储所需的认证与连接信息。
-
-```sql
-LOAD LABEL example_db.example_label
-(
- DATA INFILE("s3://bucket/example.native")
- INTO TABLE example_table
- FORMAT AS "native"
-)
-WITH S3
-(
- ...
-);
-```
-
-### 通过 TVF 使用 INSERT INTO 导入
-
-适用场景：希望直接以 SQL 方式读取远端 Native 文件并写入目标表，便于与查询、过滤、转换等逻辑组合。
-
-操作要点：
-
-- 在 TVF 参数中指定 `uri` 与 `format = "native"`。
-- 通过 `INSERT INTO ... SELECT` 将读取结果写入目标表。
-
-```sql
-INSERT INTO example_table
-SELECT *
-FROM S3
-(
- "uri" = "s3://bucket/example.native",
- "format" = "native",
- ...
-);
-```
-
-## FAQ
-
-**Q1：Native 格式是否可以用于和外部系统交换数据？**
-
-不建议。Native 是 Doris 专用的二进制格式，与外部系统不兼容。跨系统的数据交换请优先选择 CSV、JSON、Parquet、ORC 等通用格式。
-
-**Q2：为什么在 Doris 内部流转数据时推荐使用 Native 格式？**
-
-Native 格式与 Doris 内部数据结构对齐，序列化与反序列化开销最小，因此在 Doris 集群之间或备份场景下能获得最高的导入效率。
-
-**Q3：哪些导入方式支持 Native 格式？**
-
-目前支持 Stream Load、Broker Load，以及 `INSERT INTO ... FROM S3 / HDFS` TVF
这几种方式，详见上文「支持的导入方式」章节。
diff --git a/sidebars.ts b/sidebars.ts
index 03a5c7573a5..7ef9183b4a1 100644
--- a/sidebars.ts
+++ b/sidebars.ts
@@ -420,7 +420,6 @@ const sidebars: SidebarsConfig = {
'data-operate/import/file-format/json',
'data-operate/import/file-format/parquet',
'data-operate/import/file-format/orc',
- 'data-operate/import/file-format/native',
],
},
{
diff --git
a/versioned_docs/version-4.x/data-operate/import/file-format/native.md
b/versioned_docs/version-4.x/data-operate/import/file-format/native.md
deleted file mode 100644
index f27821bf5fa..00000000000
--- a/versioned_docs/version-4.x/data-operate/import/file-format/native.md
+++ /dev/null
@@ -1,120 +0,0 @@
----
-{
- "title": "Native",
- "language": "en",
- "description": "How to load Native format data in Apache Doris, suitable
for Doris internal data exchange and backup scenarios, providing the highest
load efficiency.",
- "keywords": [
- "Doris Native format",
- "Native load",
- "Stream Load Native",
- "Broker Load Native",
- "Doris internal data exchange",
- "Doris backup format"
- ]
-}
----
-
-<!-- Knowledge type: Procedure -->
-<!-- Applicable scenarios: Doris internal data flow / Backup and restore -->
-
-This document describes how to load **Native** format data files in Apache
Doris. Native is a binary data format dedicated to Doris, suitable as an
**internal data exchange and backup format** rather than a general-purpose file
exchange format. When data flows only within Doris, prefer the Native format to
achieve the highest load efficiency.
-
-> This feature is supported since version 4.1.0.
-
-## Applicable Scenarios
-
-The Native format mainly targets the following scenarios:
-
-- **Data migration between Doris clusters**: Efficiently transfer data between
different Doris clusters.
-- **Data backup and restore**: Export Doris table data to Native files for
archival, then load them back when needed.
-- **Bulk data exchange**: Move large volumes of data with the highest
efficiency within Doris internal pipelines.
-
-> Tip: If you need to exchange data with external systems, use general-purpose
formats such as CSV, JSON, Parquet, or ORC instead of Native.
-
-## Supported Load Methods
-
-The following table lists the load methods that support the Native format and
their typical uses:
-
-| Load Method | Typical Use | Documentation Link |
-| --- | --- | --- |
-| Stream Load | Push local Native files over HTTP | [Stream
Load](../import-way/stream-load-manual.md) |
-| Broker Load | Asynchronously load Native files from object storage / HDFS |
[Broker Load](../import-way/broker-load-manual.md) |
-| INSERT INTO FROM S3 TVF | Read Native files directly from S3 via SQL | [S3
TVF](../../../sql-manual/sql-functions/table-valued-functions/s3) |
-| INSERT INTO FROM HDFS TVF | Read Native files directly from HDFS via SQL |
[HDFS TVF](../../../sql-manual/sql-functions/table-valued-functions/hdfs) |
-
-## Usage Examples
-
-The following examples show how to use the Native format with different load
methods. Choose the appropriate method based on the data source (local file /
object storage / HDFS) and load mode (synchronous / asynchronous).
-
-### Load Local Native Files via Stream Load
-
-Applicable scenario: A Native file resides on the local machine or on a server
that can access the FE HTTP port, and you need a fast synchronous load.
-
-Steps:
-
-1. Prepare the Native file `example.native`.
-2. Use `curl` to push the file through the Stream Load interface, and specify
the format with the request header `format: native`.
-
-```shell
-curl --location-trusted -u <user>:<passwd> \
- -H "format: native" \
- -T example.native \
- http://<fe_host>:<fe_http_port>/api/example_db/example_table/_stream_load
-```
-
-### Load from Object Storage via Broker Load
-
-Applicable scenario: The Native file is stored in remote storage such as S3
(or an S3-compatible object store), and you need an asynchronous batch load.
-
-Key points:
-
-- Specify the Native file path in `DATA INFILE`.
-- Explicitly declare the format with `FORMAT AS "native"`.
-- Provide the authentication and connection information required to access the
object storage in `WITH S3`.
-
-```sql
-LOAD LABEL example_db.example_label
-(
- DATA INFILE("s3://bucket/example.native")
- INTO TABLE example_table
- FORMAT AS "native"
-)
-WITH S3
-(
- ...
-);
-```
-
-### Load via INSERT INTO with TVF
-
-Applicable scenario: You want to read remote Native files directly with SQL
and write them into a target table, making it easy to combine with query,
filter, and transformation logic.
-
-Key points:
-
-- Specify `uri` and `format = "native"` in the TVF parameters.
-- Use `INSERT INTO ... SELECT` to write the read result into the target table.
-
-```sql
-INSERT INTO example_table
-SELECT *
-FROM S3
-(
- "uri" = "s3://bucket/example.native",
- "format" = "native",
- ...
-);
-```
-
-## FAQ
-
-**Q1: Can the Native format be used to exchange data with external systems?**
-
-Not recommended. Native is a binary format dedicated to Doris and is not
compatible with external systems. For cross-system data exchange, prefer
general-purpose formats such as CSV, JSON, Parquet, or ORC.
-
-**Q2: Why is the Native format recommended for data flow within Doris?**
-
-The Native format aligns with Doris internal data structures, so serialization
and deserialization overhead is minimal. As a result, it delivers the highest
load efficiency between Doris clusters or in backup scenarios.
-
-**Q3: Which load methods support the Native format?**
-
-Stream Load, Broker Load, and `INSERT INTO ... FROM S3 / HDFS` TVF are
currently supported. See the "Supported Load Methods" section above for details.
diff --git a/versioned_sidebars/version-4.x-sidebars.json
b/versioned_sidebars/version-4.x-sidebars.json
index dac825d2327..fbf3dde1ead 100644
--- a/versioned_sidebars/version-4.x-sidebars.json
+++ b/versioned_sidebars/version-4.x-sidebars.json
@@ -460,8 +460,7 @@
"data-operate/import/file-format/csv",
"data-operate/import/file-format/json",
"data-operate/import/file-format/parquet",
- "data-operate/import/file-format/orc",
- "data-operate/import/file-format/native"
+ "data-operate/import/file-format/orc"
]
},
{
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
