This is an automated email from the ASF dual-hosted git repository.
JNSimba 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 82adf06104f [doc](streaming job) add OceanBase continuous load docs
(#4158)
82adf06104f is described below
commit 82adf06104f54beaf08d90c3564b3cd7caf149d1
Author: wudi <[email protected]>
AuthorDate: Mon Sep 21 14:02:50 2026 +0800
[doc](streaming job) add OceanBase continuous load docs (#4158)
## Summary
- add experimental OceanBase CDC Auto Table Creation, Schema Change, and
data type mapping documentation
- cover dev and 4.x documentation in both English and Chinese, including
sidebar and overview navigation
## Versions
- [x] dev
- [x] 4.x
- [ ] 3.x
- [ ] 2.1 or older (not covered by version/language sync gate)
## Languages
- [x] Chinese
- [x] English
## Docs Checklist
- [x] Checked by AI
- [ ] Test Cases Built
- [x] Updated required version and language counterparts, or explained
why not
- [x] If only one language changed, confirmed whether source/translation
counterparts need sync
## Validation
- `yarn docs:links:changed`
- `yarn docs:features:changed`
- `yarn docs:i18n-sync:changed`
- `git diff --check`
---
.../continuous-load-oceanbase-database.md | 205 +++++++++++++++++++++
.../streaming-job/continuous-load-overview.md | 53 +-----
.../streaming-job/data-type-mapping-oceanbase.md | 73 ++++++++
.../streaming-job/schema-change-mysql.md | 2 +-
.../streaming-job/schema-change-oceanbase.md | 76 ++++++++
.../streaming-job/schema-change-postgresql.md | 2 +-
.../docusaurus-plugin-content-docs/current.json | 4 +
.../continuous-load-oceanbase-database.md | 205 +++++++++++++++++++++
.../streaming-job/continuous-load-overview.md | 53 +-----
.../streaming-job/data-type-mapping-oceanbase.md | 73 ++++++++
.../streaming-job/schema-change-mysql.md | 2 +-
.../streaming-job/schema-change-oceanbase.md | 76 ++++++++
.../streaming-job/schema-change-postgresql.md | 2 +-
.../version-4.x.json | 4 +
.../continuous-load-oceanbase-database.md | 205 +++++++++++++++++++++
.../streaming-job/continuous-load-overview.md | 50 +----
.../streaming-job/data-type-mapping-oceanbase.md | 73 ++++++++
.../streaming-job/schema-change-mysql.md | 2 +-
.../streaming-job/schema-change-oceanbase.md | 76 ++++++++
.../streaming-job/schema-change-postgresql.md | 2 +-
sidebars.ts | 9 +
.../continuous-load-oceanbase-database.md | 205 +++++++++++++++++++++
.../streaming-job/continuous-load-overview.md | 50 +----
.../streaming-job/data-type-mapping-oceanbase.md | 73 ++++++++
.../streaming-job/schema-change-mysql.md | 2 +-
.../streaming-job/schema-change-oceanbase.md | 76 ++++++++
.../streaming-job/schema-change-postgresql.md | 2 +-
versioned_sidebars/version-4.x-sidebars.json | 9 +
28 files changed, 1488 insertions(+), 176 deletions(-)
diff --git
a/docs/data-operate/import/import-way/streaming-job/continuous-load-oceanbase-database.md
b/docs/data-operate/import/import-way/streaming-job/continuous-load-oceanbase-database.md
new file mode 100644
index 00000000000..20a29ab267b
--- /dev/null
+++
b/docs/data-operate/import/import-way/streaming-job/continuous-load-oceanbase-database.md
@@ -0,0 +1,205 @@
+---
+{
+ "title": "OceanBase CDC with Auto Table Creation",
+ "language": "en",
+ "sidebar_label": "Auto Table Creation Sync",
+ "description": "Learn how to continuously sync full and incremental data
from primary-key tables in OceanBase MySQL compatibility mode to Doris through
a Streaming Job.",
+ "keywords": [
+ "OceanBase Auto Table Creation Sync",
+ "OceanBase CDC",
+ "OBBinlog",
+ "Doris Streaming Job",
+ "continuous load",
+ "full and incremental sync",
+ "automatic table creation"
+ ]
+}
+---
+
+<!-- Knowledge type: Procedure + Configuration parameters -->
+<!-- Applicable scenario: Mirror an OceanBase database in MySQL compatibility
mode to Doris -->
+
+OceanBase CDC with Auto Table Creation uses `FROM OCEANBASE (...) TO DATABASE
(...)`. Doris reads full and incremental data through the OBBinlog service and
automatically creates Doris Unique Key tables from the upstream schemas. Use
`include_tables` to sync one table, multiple tables, or all tables in the
database.
+
+:::caution Experimental feature
+
+OceanBase CDC continuous load is available as an experimental feature starting
from Doris 4.1.4. It currently supports only OceanBase MySQL compatibility mode
and Auto Table Creation Sync. Oracle compatibility mode and SQL Mapping Sync
are not supported.
+
+:::
+
+### Applicable Scenarios
+
+- Mirror a group of OceanBase tables or an entire database to Doris.
+- Let Doris create target tables and primary keys from the upstream schemas.
+- Perform an initial full load and then continuously sync incremental changes.
+- Rename target tables or exclude columns without SQL expressions, row
filters, or data transformations.
+
+### Capabilities and Limitations
+
+| Item | Description |
+| --- | --- |
+| Compatibility mode | OceanBase MySQL compatibility mode only |
+| Sync method | Auto Table Creation Sync only; SQL Mapping Sync is not
supported |
+| Consistency semantics | At-least-once |
+| Table type | Upstream tables must have primary keys; automatically created
Doris tables use the Unique Key model |
+| Permissions | Load permission is required; Create permission is also
required when the target table does not exist |
+| Schema Change | Syncs `ADD COLUMN` and `DROP COLUMN`; see [Schema Change
Sync](./schema-change-oceanbase.md) |
+| Data types | Uses MySQL-compatible type conversion; see [Data Type
Mapping](./data-type-mapping-oceanbase.md) |
+
+## Prerequisites
+
+Before creating a job, confirm the following:
+
+1. OceanBase runs in MySQL compatibility mode. Doris validates the mode by
running `SHOW VARIABLES LIKE 'ob_compatibility_mode'` when creating the job.
+2. The OBBinlog service is deployed and available. Running `SHOW MASTER
STATUS` against its MySQL protocol endpoint returns a valid binlog file and
position.
+3. Doris FE, BE, and CDC Client can access the OBBinlog service.
+4. A compatible MySQL Connector/J driver is available, and `jdbc_url` starts
with `jdbc:mysql://`.
+5. The source account can read the tables, schemas, and binlog in the sync
scope.
+6. Every upstream table to be synced has a primary key.
+
+## Quick Start
+
+### Step 1: Create a Load Job
+
+The following example syncs the `users` and `orders` tables in `source_db`:
+
+```sql
+CREATE JOB oceanbase_db_sync
+ON STREAMING
+FROM OCEANBASE (
+ "jdbc_url" = "jdbc:mysql://127.0.0.1:2883",
+ "driver_url" = "mysql-connector-j-8.4.0.jar",
+ "driver_class" = "com.mysql.cj.jdbc.Driver",
+ "user" = "root@test",
+ "password" = "123456",
+ "database" = "source_db",
+ "include_tables" = "users,orders",
+ "offset" = "initial"
+)
+TO DATABASE target_db (
+ "table.create.properties.replication_num" = "1"
+);
+```
+
+- `jdbc_url` points to the MySQL protocol port of the OBBinlog service. Use
the port configured in your deployment.
+- `offset = "initial"` loads existing rows first and then continuously syncs
binlog changes.
+- If `include_tables` is omitted, all eligible tables in `database` are synced.
+- For a single-BE deployment, set `replication_num` to `1`. In production, set
the replica count according to the cluster size.
+
+### Step 2: Check Load Status
+
+```sql
+SELECT Name, Status, CurrentOffset, ErrorMsg
+FROM jobs("type" = "insert")
+WHERE Name = "oceanbase_db_sync";
+```
+
+When the job is running normally, `Status` is `RUNNING`:
+
+```text
++-------------------+---------+-----------------------------------------------+----------+
+| Name | Status | CurrentOffset
| ErrorMsg |
++-------------------+---------+-----------------------------------------------+----------+
+| oceanbase_db_sync | RUNNING | {"file":"binlog.000001","pos":"154", ...} |
NULL |
++-------------------+---------+-----------------------------------------------+----------+
+```
+
+### Step 3: Verify Incremental Sync
+
+After running `INSERT`, `UPDATE`, or `DELETE` against an OceanBase source
table, query the corresponding Doris table and verify that the change has been
synchronized:
+
+```sql
+SELECT * FROM target_db.users ORDER BY id;
+```
+
+For pause, resume, delete, and Task query operations, see [Continuous Load
Overview](./continuous-load-overview.md#common-operations).
+
+## Data Source Parameters
+
+| Parameter | Required | Default | Description |
+| --- | --- | --- | --- |
+| `jdbc_url` | Yes | - | JDBC connection string for the OBBinlog service. It
must start with `jdbc:mysql://`. |
+| `driver_url` | Yes | - | Path to the MySQL Connector/J driver jar. Supports
a file name, local absolute path, or HTTP URL. |
+| `driver_class` | Yes | - | MySQL JDBC driver class, for example,
`com.mysql.cj.jdbc.Driver`. |
+| `user` | Yes | - | OceanBase user name. Include tenant information using the
user name format required by OceanBase. |
+| `password` | Yes | - | OceanBase user password. |
+| `database` | Yes | - | OceanBase database name. |
+| `include_tables` | No | - | Table names to sync, separated by commas. If
omitted, all tables in the database are synced. |
+| `exclude_tables` | No | - | Table names not to sync, separated by commas.
This parameter takes effect only when `include_tables` is not set. |
+| `table.<table_name>.target_table` | No | Source table name | Sets the Doris
target table name for a source table. |
+| `table.<table_name>.exclude_columns` | No | - | Excludes non-key columns
from a source table, separated by commas. Each column must exist and cannot be
a primary key column. |
+| `offset` | No | `latest` | Startup position. `initial`: full and incremental
sync; `snapshot`: full sync only; `earliest`: start at the earliest available
binlog position; `latest`: sync only changes after the job starts. An exact
position such as `{"file":"binlog.000001","pos":"154"}` is also supported. |
+| `snapshot_split_size` | No | `40960` | Number of rows in each split during
the full-sync phase. Must be a positive integer. |
+| `snapshot_parallelism` | No | `1` | Maximum number of splits scheduled
concurrently by one Task during the full-sync phase. Must be a positive
integer. |
+| `skip_snapshot_backfill` | No | `true` | Whether to skip binlog backfill
during the snapshot phase. Auto Table Creation Sync provides at-least-once
semantics. |
+| `server_id` | No | Automatically generated | Server ID of the CDC reader.
Supports a single value such as `5400` or a closed range such as `5400-5408`.
The range must contain at least `snapshot_parallelism` IDs. |
+| `ssl_mode` | No | `disable` | SSL mode. Valid values are `disable`,
`require`, and `verify-ca`. |
+| `ssl_rootcert` | Conditionally required | - | Required when `ssl_mode` is
`verify-ca`. Use the format `FILE:<file_name>` and upload the file first with
[CREATE FILE](../../../../sql-manual/sql-statements/security/CREATE-FILE.md). |
+
+The `schema`, `slot_name`, and `publication_name` parameters are not
supported. Job creation fails if any of them is specified.
+
+## Reference Manual
+
+### Load Statement
+
+```sql
+CREATE JOB <job_name>
+[job_properties]
+ON STREAMING
+[COMMENT <comment>]
+FROM OCEANBASE (
+ [source_properties]
+)
+TO DATABASE <target_db> (
+ [target_properties]
+);
+```
+
+| Module | Description |
+| --- | --- |
+| `job_name` | Job name. |
+| `job_properties` | Common Job parameters such as `max_interval` and
`compute_group`. |
+| `comment` | Job comment. |
+| `source_properties` | OceanBase data source parameters. |
+| `target_properties` | Doris target database parameters. |
+
+### Doris Target Database Parameters
+
+| Parameter | Default | Description |
+| --- | --- | --- |
+| `table.create.properties.*` | - | Adds table properties when Doris creates a
table, for example, `table.create.properties.replication_num`. |
+| `load.strict_mode` | `false` | Whether to enable strict mode for Stream
Load. |
+| `load.max_filter_ratio` | `0` | Maximum filter ratio allowed in the sampling
window, in the range `[0, 1]`. The job is paused when the ratio exceeds this
value. |
+
+## Considerations and Best Practices
+
+- Before expanding the sync scope in production, use a small set of tables to
verify OBBinlog connectivity, type mappings, and incremental latency.
+- Use `include_tables` to define the sync scope explicitly so that unrelated
tables added later are not included automatically.
+- Exclude unsupported non-key columns with
`table.<table_name>.exclude_columns`. Primary key columns cannot be excluded.
+- Before making an unsupported schema change, pause the job, apply a
compatible change to the Doris table, and then resume the job.
+- Monitor `CurrentOffset`, `LagBytes`, and `ErrorMsg` to verify that the job
continues to make progress and has not been paused automatically.
+
+## FAQ
+
+**Q1: Is OceanBase Oracle compatibility mode supported?**
+
+No. Doris checks `ob_compatibility_mode` during job creation and rejects any
mode other than MySQL compatibility mode.
+
+**Q2: Is SQL Mapping Sync supported?**
+
+No. OceanBase currently supports only `FROM OCEANBASE (...) TO DATABASE (...)`
Auto Table Creation Sync.
+
+**Q3: How do I sync only changes that occur after the job starts?**
+
+Set `offset` to `latest`. Rows that exist before the job reaches `RUNNING` are
not loaded through a snapshot.
+
+**Q4: Is an existing target table overwritten?**
+
+No. Auto table creation skips a target table that already exists. Make sure
its primary key and column types are compatible with the source table.
+
+## Related Documents
+
+- [Continuous Load Overview](./continuous-load-overview.md)
+- [OceanBase Schema Change Sync](./schema-change-oceanbase.md)
+- [OceanBase Data Type Mapping](./data-type-mapping-oceanbase.md)
+- [CREATE STREAMING
JOB](../../../../sql-manual/sql-statements/job/CREATE-STREAMING-JOB.md)
diff --git
a/docs/data-operate/import/import-way/streaming-job/continuous-load-overview.md
b/docs/data-operate/import/import-way/streaming-job/continuous-load-overview.md
index 22273fe3f6c..268b7311dab 100644
---
a/docs/data-operate/import/import-way/streaming-job/continuous-load-overview.md
+++
b/docs/data-operate/import/import-way/streaming-job/continuous-load-overview.md
@@ -3,12 +3,13 @@
"title": "Continuous Load Overview",
"language": "en",
"sidebar_label": "Overview",
- "description": "Explore Doris Streaming Job data sources, sync modes,
consistency semantics, job states, common parameters, and operational
commands.",
+ "description": "Explore Doris Streaming Job data sources, including MySQL,
PostgreSQL, OceanBase, and S3, as well as sync modes, consistency semantics,
job states, common parameters, and operational commands.",
"keywords": [
"Doris continuous load",
"Streaming Job",
"MySQL real-time sync",
"PostgreSQL real-time sync",
+ "OceanBase real-time sync",
"S3 continuous load",
"SQL Mapping Sync",
"Auto Table Creation Sync",
@@ -44,41 +45,10 @@ Continuous load supports the following data sources and
sync modes:
| :---------- | :----------------- |
:---------------------------------------------------------------- |
:---------------------------------------------------------------------- |
:----------------------------------------------------------------------------------------------------------------------------------------
|
| MySQL | 5.6, 5.7, 8.0.x | [MySQL CDC with SQL
Mapping](./continuous-load-mysql-table.md) | [MySQL CDC with Auto Table
Creation](./continuous-load-mysql-database.md) | [Amazon RDS
MySQL](./prerequisites/amazon-rds-mysql.md) · [Amazon Aurora
MySQL](./prerequisites/amazon-aurora-mysql.md) |
| PostgreSQL | 14, 15, 16, 17 | [PostgreSQL CDC with SQL
Mapping](./continuous-load-postgresql-table.md) | [PostgreSQL CDC with Auto
Table Creation](./continuous-load-postgresql-database.md) | [Amazon RDS
PostgreSQL](./prerequisites/amazon-rds-postgresql.md) · [Amazon Aurora
PostgreSQL](./prerequisites/amazon-aurora-postgresql.md) |
-| OceanBase | MySQL compatibility mode | -
| Supported (since version 4.1.4). For the syntax, see
[OceanBase Data Source](#oceanbase-data-source) | -
|
+| OceanBase | MySQL compatibility mode | -
| [OceanBase CDC with Auto Table
Creation](./continuous-load-oceanbase-database.md) (since version 4.1.4) | -
|
| S3 | - | [S3 Continuous
Load](./continuous-load-s3.md) | -
| -
|
-For how upstream column types map to Doris types, see Data Type Mapping for
[MySQL](./data-type-mapping-mysql.md) and
[PostgreSQL](./data-type-mapping-postgresql.md). OceanBase reuses the MySQL
type mapping.
-
-### OceanBase Data Source
-
-> Supported since version 4.1.4.
-
-To use OceanBase as a CDC data source for continuous load, use the `FROM
OCEANBASE (...)` clause. Its properties are the same as those of the MySQL data
source:
-
-```sql
-CREATE JOB oceanbase_sync ON STREAMING
-FROM OCEANBASE (
- "jdbc_url" = "jdbc:mysql://<host>:<port>",
- "driver_url" = "<driver_jar_url>",
- "driver_class" = "com.mysql.cj.jdbc.Driver",
- "user" = "<user>",
- "password" = "<password>",
- "database" = "<ob_database>",
- "include_tables" = "t1,t2",
- "offset" = "initial"
-)
-TO DATABASE <doris_db> (
- "table.create.properties.replication_num" = "1"
-);
-```
-
-Limitations:
-
-- `jdbc_url` must start with `jdbc:mysql://`, otherwise the job fails with
`OceanBase jdbc_url must start with 'jdbc:mysql://'`.
-- Only the **MySQL compatibility mode** of OceanBase is supported. When the
job is created, Doris runs `SHOW VARIABLES LIKE 'ob_compatibility_mode'` to
detect the mode; the Oracle compatibility mode fails with `OceanBase Oracle
compatibility mode is not supported for streaming jobs`.
-- The `schema`, `slot_name`, and `publication_name` properties are not
supported. Specifying any of them fails with `Property '<key>' is not supported
for OceanBase`.
-- `database` is required.
-- `jdbc_url` parameters are normalized in the same way as for MySQL. See [JDBC
URL Parameter
Normalization](./data-type-mapping-mysql.md#jdbc-url-parameter-normalization).
+For how upstream column types map to Doris types, see Data Type Mapping for
[MySQL](./data-type-mapping-mysql.md),
[PostgreSQL](./data-type-mapping-postgresql.md), and
[OceanBase](./data-type-mapping-oceanbase.md).
## How to Choose a Sync Method
@@ -103,6 +73,7 @@ SQL Mapping Sync and Auto Table Creation Sync are two
continuous load methods wi
- **You need to apply SQL processing to the data, or you have strict
requirements for exactly-once semantics** -> choose **SQL Mapping Sync**
- **You want Doris to create tables automatically and sync a group of tables
with one configuration** -> choose **Auto Table Creation Sync**
+- **The data source is OceanBase** -> currently, only Auto Table Creation Sync
in MySQL compatibility mode is supported
- **The data source is S3 object storage** -> only SQL Mapping Sync is
supported (using the S3 TVF)
## Job State Transitions
@@ -165,7 +136,7 @@ Result columns:
| LoadStatistic | Job statistics
|
| ErrorMsg | Error message of the Job
|
| JobRuntimeMsg | Runtime hints of the Job
|
-| LagBytes | Number of backlog bytes in the source log (MySQL binlog
/ PostgreSQL WAL). `-1` means the value is currently unavailable, for example
for an S3 data source or during the full snapshot phase. **Since version
4.1.4**, this column replaces the former `Lag` column (in seconds) and is
reported in bytes |
+| LagBytes | Number of backlog bytes in the source log (MySQL /
OceanBase binlog or PostgreSQL WAL). `-1` means the value is currently
unavailable, for example for an S3 data source or during the full snapshot
phase. **Since version 4.1.4**, this column replaces the former `Lag` column
(in seconds) and is reported in bytes |
| LastSourceEventTimestamp | Timestamp (in Unix seconds) of the latest source
event recorded in the committed offset. Empty when unavailable. **Added in
version 4.1.4** |
| LastTaskSuccessTime | Time when the most recent Task completed successfully
|
@@ -232,7 +203,7 @@ DROP JOB WHERE jobName = <job_name>;
### Job Common Load Configuration Parameters
-Configure the following parameters through `CREATE JOB ... PROPERTIES (...)`.
Unless otherwise specified, they can be used by both SQL Mapping Sync and Auto
Table Creation Sync for MySQL and PostgreSQL.
+Configure the following parameters through `CREATE JOB ... PROPERTIES (...)`.
Unless otherwise specified, MySQL, PostgreSQL, and OceanBase continuous load
jobs can use them.
| Parameter | Default | Description |
| --- | --- | --- |
@@ -240,7 +211,7 @@ Configure the following parameters through `CREATE JOB ...
PROPERTIES (...)`. Un
| `compute_group` | Current session or user default compute group | Supported
only in compute-storage decoupled mode. Specifies the compute group in which
the job runs. An explicitly configured value cannot be empty, and the user must
have the USAGE privilege on the compute group. Job creation fails if this
parameter is not set and neither the current session nor the user has an
available default compute group. |
| `session.<variable_name>` | Default value of the corresponding session
variable | Supported only in TVF mode. Sets a session variable for the Job's
INSERT task, for example, `session.insert_max_filter_ratio`. The variable name
and value must be valid Doris session variables. |
-When used as a Job Property, `offset` does not set the initial position of a
MySQL or PostgreSQL job. When creating a job, set the initial position in the
source parameters of `FROM MYSQL`, `FROM POSTGRES`, or `cdc_stream(...)`. After
pausing a CDC job, you can reset its position through `ALTER JOB ... PROPERTIES
("offset" = '<json_offset>')`. MySQL uses
`{"file":"binlog.000001","pos":"154"}`, and PostgreSQL uses
`{"lsn":"12345678"}`. `ALTER JOB` accepts only exact JSON offsets.
+When used as a Job Property, `offset` does not set the initial position of a
CDC job. When creating a job, set the initial position in the source parameters
of `FROM MYSQL`, `FROM POSTGRES`, `FROM OCEANBASE`, or `cdc_stream(...)`. After
pausing a CDC job, you can reset its position through `ALTER JOB ... PROPERTIES
("offset" = '<json_offset>')`. MySQL and OceanBase use
`{"file":"binlog.000001","pos":"154"}`, and PostgreSQL uses
`{"lsn":"12345678"}`. `ALTER JOB` accepts only exact JSON offsets.
## Limitations
@@ -256,13 +227,9 @@ Only upstream tables **with a primary key** can be
synchronized (both sync metho
DDL sync applies **only to the [Auto Table Creation Sync
method](#capability-comparison)**; the [SQL Mapping Sync
method](#capability-comparison) does not sync any DDL — the `cdc_stream()`
table function always forces `schema_change_enabled` to `false`.
-- **MySQL and PostgreSQL**: only `ADD COLUMN` and `DROP COLUMN` are synced.
**Column type changes, `RENAME COLUMN`, and primary key / constraint / index /
partition changes are NOT synced** — apply them manually in Doris. For
source-specific behavior and limitations, see [MySQL Schema Change
Sync](./schema-change-mysql.md) and [PostgreSQL Schema Change
Sync](./schema-change-postgresql.md).
-
-You can turn this capability off with the Job property `schema_change_enabled`:
+- **MySQL, PostgreSQL, and OceanBase**: only `ADD COLUMN` and `DROP COLUMN`
are synced. **Column type changes, `RENAME COLUMN`, and primary key /
constraint / index / partition changes are NOT synced** — apply them manually
in Doris. For source-specific behavior and limitations, see Schema Change Sync
for [MySQL](./schema-change-mysql.md),
[PostgreSQL](./schema-change-postgresql.md), and
[OceanBase](./schema-change-oceanbase.md).
-| Parameter | Applicable data sources | Default | Description |
-| --- | --- | --- | --- |
-| `schema_change_enabled` | MySQL, PostgreSQL | `true` | Whether to
automatically sync upstream `ADD COLUMN` / `DROP COLUMN`. Supported since
version 4.1.4 |
+Auto Table Creation Sync enables Schema Change Sync by default. Doris
currently does not provide a SQL property to disable it.
## FAQ
diff --git
a/docs/data-operate/import/import-way/streaming-job/data-type-mapping-oceanbase.md
b/docs/data-operate/import/import-way/streaming-job/data-type-mapping-oceanbase.md
new file mode 100644
index 00000000000..16ea4b15cf2
--- /dev/null
+++
b/docs/data-operate/import/import-way/streaming-job/data-type-mapping-oceanbase.md
@@ -0,0 +1,73 @@
+---
+{
+ "title": "OceanBase Data Type Mapping",
+ "language": "en",
+ "sidebar_label": "Data Type Mapping",
+ "description": "Learn how MySQL-compatible OceanBase column types map to
Doris column types during CDC Auto Table Creation Sync."
+}
+---
+
+<!-- Knowledge type: Reference / data type mapping -->
+
+OceanBase CDC continuous load supports only MySQL compatibility mode and uses
the MySQL type conversion path. The following table shows how OceanBase column
types map to Doris column types during automatic table creation.
+
+:::caution Experimental feature
+
+OceanBase CDC continuous load is available as an experimental feature starting
from Doris 4.1.4.
+
+:::
+
+## JDBC URL Parameter Normalization
+
+When you create an OceanBase Streaming Job, Doris automatically appends the
following parameters to `jdbc_url` unless you set them explicitly:
+
+| Parameter | Injected Value | Effect |
+| --- | --- | --- |
+| `tinyInt1isBit` | `false` | Reads `TINYINT(1)` as `TINYINT` (`1` / `0`)
instead of `BOOLEAN` (`true` / `false`). |
+| `yearIsDateType` | `false` | Reads `YEAR` as an integer year instead of a
date. |
+| `useUnicode` | `true` | Uses Unicode encoding. |
+| `characterEncoding` | `utf-8` | Uses UTF-8 as the character set. |
+
+If any of these parameters is set explicitly in `jdbc_url`, Doris keeps the
configured value.
+
+## OceanBase to Doris
+
+| OceanBase Type (MySQL compatibility mode) | Doris Type | Notes |
+| --- | --- | --- |
+| `BOOLEAN` / `TINYINT(1)` | `TINYINT` | Values are `1` / `0` by default. Set
`tinyInt1isBit=true` to change the JDBC read behavior. |
+| `TINYINT` | `TINYINT` | `UNSIGNED` → `SMALLINT` |
+| `SMALLINT` | `SMALLINT` | `UNSIGNED` → `INT` |
+| `MEDIUMINT` | `INT` | `UNSIGNED` → `INT` |
+| `INT` | `INT` | `UNSIGNED` → `BIGINT` |
+| `BIGINT` | `BIGINT` | `UNSIGNED` → `LARGEINT` |
+| `YEAR` | `SMALLINT` | Read as an integer year; zero year (`0000`) is
preserved as `0`. |
+| `FLOAT` | `FLOAT` | |
+| `DOUBLE` | `DOUBLE` | |
+| `DECIMAL(p,s)` | `DECIMAL(p,s)` | Very high precision falls back to
`STRING`. |
+| `DATE` | `DATE` | |
+| `DATETIME` | `DATETIME(s)` | Preserves microsecond scale from 0 to 6. |
+| `TIMESTAMP` | `DATETIME(s)` | Normalized to the server time zone. |
+| `TIME` | `STRING` | Stored as a string, for example, `12:34:56.000000`. |
+| `CHAR` | `CHAR` | |
+| `VARCHAR` | `VARCHAR` | |
+| `TINYTEXT` / `TEXT` / `MEDIUMTEXT` / `LONGTEXT` | `STRING` | |
+| `BINARY` / `VARBINARY` / `TINYBLOB` / `BLOB` / `MEDIUMBLOB` / `LONGBLOB` |
`STRING` | Base64-encoded string. |
+| `BIT(1)` | `BOOLEAN` | |
+| `BIT(n>1)` | `STRING` | Base64-encoded string. |
+| `JSON` | `STRING` | Stored as JSON text. |
+| `ENUM` | `STRING` | Resolved to the label value. |
+| `SET` | `STRING` | Resolved to comma-separated labels. |
+| Spatial types (`GEOMETRY`, `POINT`, and others) and other types | Not
supported | Automatic table creation fails for a table containing such a
column. Exclude a non-key column with `table.<table_name>.exclude_columns`. |
+
+## Considerations
+
+- Type mapping is based on metadata returned by OceanBase through MySQL
Connector/J.
+- Unsupported types do not fall back to an arbitrary Doris type. Verify the
target table schema before creating a production job.
+- `TIMESTAMP` is affected by the source time zone and the `serverTimezone`
JDBC URL parameter. Set and verify the time zone explicitly for cross-time-zone
deployments.
+- Primary key columns cannot be excluded through
`table.<table_name>.exclude_columns`.
+
+## Related Documents
+
+- [OceanBase CDC with Auto Table
Creation](./continuous-load-oceanbase-database.md)
+- [OceanBase Schema Change Sync](./schema-change-oceanbase.md)
+- [Continuous Load Overview](./continuous-load-overview.md)
diff --git
a/docs/data-operate/import/import-way/streaming-job/schema-change-mysql.md
b/docs/data-operate/import/import-way/streaming-job/schema-change-mysql.md
index d4785d657f7..31ca1d6de1b 100644
--- a/docs/data-operate/import/import-way/streaming-job/schema-change-mysql.md
+++ b/docs/data-operate/import/import-way/streaming-job/schema-change-mysql.md
@@ -40,7 +40,7 @@ MySQL Schema Change Sync is supported from Doris 4.1.4.
- Column positions specified by `FIRST` and `AFTER` are not synchronized to
Doris. New columns are appended after the existing Doris columns.
- `CHANGE COLUMN`, `MODIFY COLUMN`, `RENAME COLUMN`, DEFAULT changes, and
`NULL` / `NOT NULL` constraint changes are not synchronized automatically.
Before performing these operations, pause the continuous load job, change the
Doris target table manually, verify that both schemas are compatible, and then
resume the job.
- Primary key, index, partition, table name, and other table-level schema
changes are not synchronized automatically.
-- You can disable automatic schema change synchronization with the Job
property `schema_change_enabled` (default `true`, supported since version
4.1.4). The `cdc_stream()` table function (SQL Mapping Sync) always forces this
property to `false`.
+- Auto Table Creation Sync enables Schema Change Sync by default. Doris
currently does not provide a SQL property to disable it. The `cdc_stream()`
table function (SQL Mapping Sync) disables Schema Change Sync internally.
## Related Docs
diff --git
a/docs/data-operate/import/import-way/streaming-job/schema-change-oceanbase.md
b/docs/data-operate/import/import-way/streaming-job/schema-change-oceanbase.md
new file mode 100644
index 00000000000..958b3be3531
--- /dev/null
+++
b/docs/data-operate/import/import-way/streaming-job/schema-change-oceanbase.md
@@ -0,0 +1,76 @@
+---
+{
+ "title": "OceanBase Schema Change Sync",
+ "language": "en",
+ "sidebar_label": "Schema Change Sync",
+ "description": "Learn which OceanBase schema changes are supported by CDC
Auto Table Creation Sync, how Doris applies them, and their limitations.",
+ "keywords": [
+ "OceanBase Schema Change",
+ "OceanBase CDC",
+ "Auto Table Creation Sync",
+ "continuous load",
+ "ADD COLUMN",
+ "DROP COLUMN"
+ ]
+}
+---
+
+<!-- Knowledge type: Concept -->
+<!-- Applicable scenario: Upstream schema changes during OceanBase Auto Table
Creation Sync -->
+
+OceanBase Schema Change Sync automatically applies upstream column changes to
Doris target tables during continuous load. This capability applies only to
[OceanBase CDC with Auto Table
Creation](./continuous-load-oceanbase-database.md).
+
+:::caution Experimental feature
+
+OceanBase Schema Change Sync is available as an experimental feature starting
from Doris 4.1.4 and supports only MySQL compatibility mode.
+
+:::
+
+OceanBase uses the MySQL CDC schema change processing path, so its supported
changes and behavior are the same as for MySQL.
+
+## Supported Schema Changes
+
+| OceanBase operation | Doris behavior |
+| --- | --- |
+| `ADD COLUMN` | Adds a column with the same name and a type defined by
[OceanBase Data Type Mapping](./data-type-mapping-oceanbase.md), and copies the
column comment. DEFAULT and `NOT NULL` constraints are not copied, and
historical rows are not backfilled. Subsequent rows use the actual values
written by OceanBase to the binlog. |
+| `DROP COLUMN` | Drops the column with the same name. |
+
+## Considerations
+
+- If an added column already exists or a dropped column does not exist, Doris
skips the operation so that retries do not fail the job.
+- Column positions specified by `FIRST` and `AFTER` are not synchronized to
Doris. New columns are appended after existing Doris columns.
+- `CHANGE COLUMN`, `MODIFY COLUMN`, `RENAME COLUMN`, DEFAULT changes, and
`NULL` / `NOT NULL` constraint changes are not synchronized automatically.
+- Primary key, index, partition, table name, and other table-level schema
changes are not synchronized automatically.
+- Before an unsupported schema change, pause the continuous load job, change
the Doris target table manually, verify that both schemas are compatible, and
then resume the job.
+- Auto Table Creation Sync enables Schema Change Sync by default. Doris
currently does not provide a SQL property to disable it.
+
+## Example
+
+Add a column to an OceanBase source table:
+
+```sql
+ALTER TABLE source_db.users ADD COLUMN city VARCHAR(50);
+INSERT INTO source_db.users VALUES (2, 'Alice', 'Hangzhou');
+```
+
+After the job processes the incremental data, the `city` column appears in the
Doris target table:
+
+```sql
+DESC target_db.users;
+```
+
+```text
++-------+--------------+------+-------+---------+-------+
+| Field | Type | Null | Key | Default | Extra |
++-------+--------------+------+-------+---------+-------+
+| id | int | No | true | NULL | |
+| name | varchar(100) | Yes | false | NULL | NONE |
+| city | varchar(50) | Yes | false | NULL | NONE |
++-------+--------------+------+-------+---------+-------+
+```
+
+## Related Documents
+
+- [OceanBase CDC with Auto Table
Creation](./continuous-load-oceanbase-database.md)
+- [OceanBase Data Type Mapping](./data-type-mapping-oceanbase.md)
+- [Continuous Load Overview](./continuous-load-overview.md)
diff --git
a/docs/data-operate/import/import-way/streaming-job/schema-change-postgresql.md
b/docs/data-operate/import/import-way/streaming-job/schema-change-postgresql.md
index 4fd65efd667..bb5d9031dc2 100644
---
a/docs/data-operate/import/import-way/streaming-job/schema-change-postgresql.md
+++
b/docs/data-operate/import/import-way/streaming-job/schema-change-postgresql.md
@@ -41,7 +41,7 @@ PostgreSQL Schema Change Sync is supported from Doris 4.1.0.
- If an added column already exists or a dropped column does not exist, Doris
skips the operation so that a retry does not fail the job.
- If one schema change adds and drops columns at the same time, Doris treats
it as a possible column rename and does not automatically change the target
table. This prevents accidental data loss.
- Column renames, column type changes, DEFAULT changes, and `NULL` / `NOT
NULL` constraint changes are not synchronized automatically. Pause the
continuous load job, change the Doris target table manually, verify that both
schemas are compatible, and then resume the job.
-- You can disable automatic schema change synchronization with the Job
property `schema_change_enabled` (default `true`, supported since version
4.1.4). The `cdc_stream()` table function (SQL Mapping Sync) always forces this
property to `false`.
+- Auto Table Creation Sync enables Schema Change Sync by default. Doris
currently does not provide a SQL property to disable it. The `cdc_stream()`
table function (SQL Mapping Sync) disables Schema Change Sync internally.
:::caution Behavior change (4.1.4)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current.json
b/i18n/zh-CN/docusaurus-plugin-content-docs/current.json
index d0d61321851..2fff80f92e4 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current.json
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current.json
@@ -735,6 +735,10 @@
"message": "优化技术原理",
"description": "The label for category Optimization Technology Principles
in sidebar docs"
},
+ "sidebar.docs.category.OceanBase (Experimental)": {
+ "message": "OceanBase（实验性）",
+ "description": "The label for category OceanBase (Experimental) in sidebar
docs"
+ },
"sidebar.docs.category.Paimon Catalog": {
"message": "Paimon Catalog",
"description": "The label for category Paimon Catalog in sidebar docs"
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-way/streaming-job/continuous-load-oceanbase-database.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-way/streaming-job/continuous-load-oceanbase-database.md
new file mode 100644
index 00000000000..f5bcc4bb8df
--- /dev/null
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-way/streaming-job/continuous-load-oceanbase-database.md
@@ -0,0 +1,205 @@
+---
+{
+ "title": "OceanBase CDC 自动建表同步",
+ "language": "zh-CN",
+ "sidebar_label": "自动建表同步",
+ "description": "介绍如何通过 Doris Streaming Job 将 OceanBase MySQL
兼容模式下主键表的全量与增量数据持续同步到 Doris。",
+ "keywords": [
+ "OceanBase 自动建表同步",
+ "OceanBase CDC",
+ "OBBinlog",
+ "Doris Streaming Job",
+ "持续导入",
+ "全量加增量同步",
+ "自动建表"
+ ]
+}
+---
+
+<!-- 知识类型: 操作步骤 + 配置参数 -->
+<!-- 适用场景: OceanBase MySQL 兼容模式整库镜像同步到 Doris -->
+
+OceanBase CDC 自动建表同步通过 `FROM OCEANBASE (...) TO DATABASE (...)` 实现。Doris 从
OBBinlog 服务读取 OceanBase 的全量和增量数据，并根据上游表结构自动创建 Doris 主键表。可以通过 `include_tables`
同步一张、多张或全部表。
+
+:::caution 实验性功能
+
+OceanBase CDC 持续导入自 Doris 4.1.4 起作为实验性功能提供。目前仅支持 OceanBase 的 MySQL
兼容模式和自动建表同步，不支持 Oracle 兼容模式与 SQL 映射同步。
+
+:::
+
+### 适用场景
+
+- 将 OceanBase 中的一组表或整个数据库镜像到 Doris。
+- 由 Doris 根据上游表结构和主键自动创建目标表。
+- 需要先完成全量初始化，再持续同步增量变更。
+- 只需要目标表重命名或列裁剪，不需要 SQL 表达式、行过滤或数据转换。
+
+### 能力与限制
+
+| 项目 | 说明 |
+| --- | --- |
+| 兼容模式 | 仅支持 OceanBase MySQL 兼容模式 |
+| 同步方式 | 仅支持自动建表同步，不支持 SQL 映射同步 |
+| 一致性语义 | at-least-once |
+| 表类型 | 上游表必须有主键；自动创建的 Doris 表为主键模型表（Unique Key） |
+| 权限要求 | 需要 Load 权限；目标表不存在时还需要 Create 权限 |
+| Schema Change | 支持同步 `ADD COLUMN` 和 `DROP COLUMN`，详见 [Schema Change
同步](./schema-change-oceanbase.md) |
+| 数据类型 | 复用 MySQL 兼容类型映射，详见 [数据类型映射](./data-type-mapping-oceanbase.md) |
+
+## 前置准备
+
+创建作业前，请确认：
+
+1. OceanBase 运行在 MySQL 兼容模式。Doris 创建作业时会执行 `SHOW VARIABLES LIKE
'ob_compatibility_mode'` 进行校验。
+2. OBBinlog 服务已部署并可用，通过其 MySQL 协议地址执行 `SHOW MASTER STATUS` 能返回有效的 Binlog
文件名和位点。
+3. Doris FE、BE 与 CDC Client 均可访问 OBBinlog 服务。
+4. 已准备兼容的 MySQL Connector/J 驱动；`jdbc_url` 必须以 `jdbc:mysql://` 开头。
+5. 源端账号可以读取待同步表、表结构和 Binlog。
+6. 待同步的上游表具有主键。
+
+## 快速上手
+
+### 第一步：创建导入作业
+
+以下示例同步 `source_db` 中的 `users` 和 `orders` 表：
+
+```sql
+CREATE JOB oceanbase_db_sync
+ON STREAMING
+FROM OCEANBASE (
+ "jdbc_url" = "jdbc:mysql://127.0.0.1:2883",
+ "driver_url" = "mysql-connector-j-8.4.0.jar",
+ "driver_class" = "com.mysql.cj.jdbc.Driver",
+ "user" = "root@test",
+ "password" = "123456",
+ "database" = "source_db",
+ "include_tables" = "users,orders",
+ "offset" = "initial"
+)
+TO DATABASE target_db (
+ "table.create.properties.replication_num" = "1"
+);
+```
+
+- `jdbc_url` 应指向 OBBinlog 服务的 MySQL 协议端口，具体端口以实际部署为准。
+- `offset = "initial"` 表示先同步存量数据，再持续同步 Binlog 增量。
+- `include_tables` 未设置时，同步 `database` 中所有符合要求的表。
+- 单 BE 部署需要将 `replication_num` 设为 `1`；生产环境请按集群规模设置副本数。
+
+### 第二步：查看导入状态
+
+```sql
+SELECT Name, Status, CurrentOffset, ErrorMsg
+FROM jobs("type" = "insert")
+WHERE Name = "oceanbase_db_sync";
+```
+
+作业正常运行时，`Status` 为 `RUNNING`：
+
+```text
++-------------------+---------+------------------------------------------------+----------+
+| Name | Status | CurrentOffset
| ErrorMsg |
++-------------------+---------+------------------------------------------------+----------+
+| oceanbase_db_sync | RUNNING | {"file":"binlog.000001","pos":"154", ...} |
NULL |
++-------------------+---------+------------------------------------------------+----------+
+```
+
+### 第三步：验证增量同步
+
+在 OceanBase 源表执行 `INSERT`、`UPDATE` 或 `DELETE` 后，查询对应 Doris 表，确认变更已同步：
+
+```sql
+SELECT * FROM target_db.users ORDER BY id;
+```
+
+更多暂停、恢复、删除和 Task 查询操作请参见[持续导入概览](./continuous-load-overview.md#通用操作)。
+
+## 数据源参数
+
+| 参数 | 是否必填 | 默认值 | 说明 |
+| --- | --- | --- | --- |
+| `jdbc_url` | 是 | - | OBBinlog 服务的 JDBC 连接串，必须以 `jdbc:mysql://` 开头。 |
+| `driver_url` | 是 | - | MySQL Connector/J 驱动 jar 包路径，支持文件名、本地绝对路径或 HTTP URL。 |
+| `driver_class` | 是 | - | MySQL JDBC 驱动类名，例如 `com.mysql.cj.jdbc.Driver`。 |
+| `user` | 是 | - | OceanBase 用户名；租户信息按 OceanBase 的用户名格式填写。 |
+| `password` | 是 | - | OceanBase 用户密码。 |
+| `database` | 是 | - | OceanBase 数据库名。 |
+| `include_tables` | 否 | - | 要同步的表名，多个表用逗号分隔；不设置时同步数据库中的全部表。 |
+| `exclude_tables` | 否 | - | 不同步的表名，多个表用逗号分隔；仅在未设置 `include_tables` 时生效。 |
+| `table.<table_name>.target_table` | 否 | 源表名 | 为指定源表设置 Doris 目标表名。 |
+| `table.<table_name>.exclude_columns` | 否 | - |
排除指定源表中的非主键列，多个列用逗号分隔。列必须存在，且不能排除主键列。 |
+| `offset` | 否 | `latest` | `initial`：全量 +
增量；`snapshot`：仅全量；`earliest`：从当前可用的最早 Binlog 位点开始；`latest`：仅同步作业启动后的增量；也可使用
`{"file":"binlog.000001","pos":"154"}` 形式的精确位点。 |
+| `snapshot_split_size` | 否 | `40960` | 全量阶段每个 split 包含的行数，必须为正整数。 |
+| `snapshot_parallelism` | 否 | `1` | 全量阶段单个 Task 最多并行调度的 split 数，必须为正整数。 |
+| `skip_snapshot_backfill` | 否 | `true` | 是否跳过快照期间的 Binlog 回填。自动建表同步采用
at-least-once 语义。 |
+| `server_id` | 否 | 自动生成 | CDC Reader 的 server ID，可设置单值（如 `5400`）或闭区间（如
`5400-5408`）；区间内 ID 数量不得小于 `snapshot_parallelism`。 |
+| `ssl_mode` | 否 | `disable` | SSL 模式，可选值为 `disable`、`require`、`verify-ca`。 |
+| `ssl_rootcert` | 条件必填 | - | `ssl_mode` 为 `verify-ca` 时必填，格式为
`FILE:<file_name>`；需先通过 [CREATE
FILE](../../../../sql-manual/sql-statements/security/CREATE-FILE.md) 上传。 |
+
+不支持 `schema`、`slot_name` 和 `publication_name` 参数。指定这些参数时，作业创建失败。
+
+## 参考手册
+
+### 导入命令
+
+```sql
+CREATE JOB <job_name>
+[job_properties]
+ON STREAMING
+[COMMENT <comment>]
+FROM OCEANBASE (
+ [source_properties]
+)
+TO DATABASE <target_db> (
+ [target_properties]
+);
+```
+
+| 模块 | 说明 |
+| --- | --- |
+| `job_name` | 作业名称。 |
+| `job_properties` | Job 通用参数，例如 `max_interval` 和 `compute_group`。 |
+| `comment` | 作业备注。 |
+| `source_properties` | OceanBase 数据源参数。 |
+| `target_properties` | Doris 目标库参数。 |
+
+### Doris 目标库参数
+
+| 参数 | 默认值 | 说明 |
+| --- | --- | --- |
+| `table.create.properties.*` | - | 自动建表时附加的表属性，例如
`table.create.properties.replication_num`。 |
+| `load.strict_mode` | `false` | 是否为 Stream Load 开启严格模式。 |
+| `load.max_filter_ratio` | `0` | 采样窗口内允许的最大过滤率，范围为 `[0, 1]`；超过该值时作业暂停。 |
+
+## 注意事项与最佳实践
+
+- 生产作业建议先用少量表验证 OBBinlog 连通性、类型映射和增量延迟，再扩大同步范围。
+- 使用 `include_tables` 明确限定同步范围，避免数据库中新增的无关表进入作业。
+- 对不支持的列类型，可通过 `table.<table_name>.exclude_columns` 排除；不能排除主键列。
+- 修改不受支持的表结构前，先暂停作业，在 Doris 端完成兼容变更后再恢复。
+- 定期检查 `CurrentOffset`、`LagBytes` 和 `ErrorMsg`，确认作业持续推进且没有被自动暂停。
+
+## FAQ
+
+**Q1：是否支持 OceanBase Oracle 兼容模式？**
+
+不支持。创建作业时 Doris 会检查 `ob_compatibility_mode`，非 MySQL 兼容模式会直接拒绝创建。
+
+**Q2：是否支持 SQL 映射同步？**
+
+不支持。OceanBase 当前仅支持 `FROM OCEANBASE (...) TO DATABASE (...)` 自动建表同步。
+
+**Q3：如何只同步作业启动后的增量数据？**
+
+将 `offset` 设置为 `latest`。在作业进入 `RUNNING` 后再写入的数据会被同步，已有数据不会执行快照导入。
+
+**Q4：目标表已存在时会被覆盖吗？**
+
+不会。自动建表阶段会跳过已存在的目标表；请确保其主键和列类型与源表兼容。
+
+## 相关文档
+
+- [持续导入概览](./continuous-load-overview.md)
+- [OceanBase Schema Change 同步](./schema-change-oceanbase.md)
+- [OceanBase 数据类型映射](./data-type-mapping-oceanbase.md)
+- [CREATE STREAMING
JOB](../../../../sql-manual/sql-statements/job/CREATE-STREAMING-JOB.md)
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-way/streaming-job/continuous-load-overview.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-way/streaming-job/continuous-load-overview.md
index 3510bd7a5e9..c6759b65b80 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-way/streaming-job/continuous-load-overview.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-way/streaming-job/continuous-load-overview.md
@@ -3,12 +3,13 @@
"title": "持续导入概览",
"language": "zh-CN",
"sidebar_label": "概览",
- "description": "了解 Doris Streaming Job 持续导入的完整能力，包括 MySQL、PostgreSQL 和 S3
数据源，SQL 映射与自动建表同步的选型、一致性语义、作业状态机、通用参数及日常运维操作。",
+ "description": "了解 Doris Streaming Job 持续导入的完整能力，包括
MySQL、PostgreSQL、OceanBase 和 S3 数据源，SQL 映射与自动建表同步的选型、一致性语义、作业状态机、通用参数及日常运维操作。",
"keywords": [
"Doris 持续导入",
"Streaming Job",
"MySQL 实时同步",
"PostgreSQL 实时同步",
+ "OceanBase 实时同步",
"S3 持续导入",
"SQL 映射同步",
"自动建表同步",
@@ -44,41 +45,10 @@ Doris 支持通过 **Streaming Job** 的方式，从多种数据源持续导入
| :--------- | :---------------- |
:-------------------------------------------------------------------- |
:-------------------------------------------------------------------------- |
:----------------------------------------------------------------------------------------------------------------------------------------
|
| MySQL | 5.6、5.7、8.0.x | [MySQL CDC SQL
映射同步](./continuous-load-mysql-table.md) | [MySQL CDC
自动建表同步](./continuous-load-mysql-database.md) | [Amazon RDS
MySQL](./prerequisites/amazon-rds-mysql.md) · [Amazon Aurora
MySQL](./prerequisites/amazon-aurora-mysql.md) |
| PostgreSQL | 14、15、16、17 | [PostgreSQL CDC SQL
映射同步](./continuous-load-postgresql-table.md) | [PostgreSQL CDC
自动建表同步](./continuous-load-postgresql-database.md) | [Amazon RDS
PostgreSQL](./prerequisites/amazon-rds-postgresql.md) · [Amazon Aurora
PostgreSQL](./prerequisites/amazon-aurora-postgresql.md) |
-| OceanBase | MySQL 兼容模式 | -
| 支持（自 4.1.4 版本起），语法见 [OceanBase 数据源](#oceanbase-数据源)
| -
|
+| OceanBase | MySQL 兼容模式 | -
| [OceanBase CDC
自动建表同步](./continuous-load-oceanbase-database.md)（自 4.1.4 版本起） | -
|
| S3 | - | [S3 持续导入](./continuous-load-s3.md)
| -
| -
|
-上游列类型如何映射为 Doris 类型，见 [MySQL](./data-type-mapping-mysql.md) /
[PostgreSQL](./data-type-mapping-postgresql.md) 数据类型映射。OceanBase 复用 MySQL 的类型映射。
-
-### OceanBase 数据源
-
-> 自 4.1.4 版本开始支持。
-
-OceanBase 作为持续导入的 CDC 数据源，使用 `FROM OCEANBASE (...)` 子句，属性与 MySQL 数据源一致：
-
-```sql
-CREATE JOB oceanbase_sync ON STREAMING
-FROM OCEANBASE (
- "jdbc_url" = "jdbc:mysql://<host>:<port>",
- "driver_url" = "<driver_jar_url>",
- "driver_class" = "com.mysql.cj.jdbc.Driver",
- "user" = "<user>",
- "password" = "<password>",
- "database" = "<ob_database>",
- "include_tables" = "t1,t2",
- "offset" = "initial"
-)
-TO DATABASE <doris_db> (
- "table.create.properties.replication_num" = "1"
-);
-```
-
-使用限制：
-
-- `jdbc_url` 必须以 `jdbc:mysql://` 开头，否则报错 `OceanBase jdbc_url must start with
'jdbc:mysql://'`；
-- 只支持 OceanBase 的 **MySQL 兼容模式**。作业创建时会执行 `SHOW VARIABLES LIKE
'ob_compatibility_mode'` 探测；Oracle 兼容模式会报错 `OceanBase Oracle compatibility mode
is not supported for streaming jobs`；
-- 不支持 `schema`、`slot_name`、`publication_name` 属性，指定后会报错 `Property '<key>' is
not supported for OceanBase`；
-- `database` 为必填项；
-- `jdbc_url` 的参数归一化规则与 MySQL 一致，详见
[数据类型映射](./data-type-mapping-mysql.md#jdbc-url-参数归一化)。
+上游列类型如何映射为 Doris 类型，见
[MySQL](./data-type-mapping-mysql.md)、[PostgreSQL](./data-type-mapping-postgresql.md)和
[OceanBase](./data-type-mapping-oceanbase.md) 数据类型映射。
## 如何选择同步方式
@@ -103,6 +73,7 @@ SQL 映射同步和自动建表同步是两种**实现机制完全不同**的持
- **需要对数据做 SQL 加工，或对精确一次语义有严格要求** → 选 **SQL 映射同步**
- **希望 Doris 自动建表、一次配置同步一组表** → 选 **自动建表同步**
+- **数据源是 OceanBase** → 目前仅支持 MySQL 兼容模式下的自动建表同步
- **数据源是 S3 对象存储** → 只支持 SQL 映射同步（S3 TVF 方式）
## 作业状态流转
@@ -165,7 +136,7 @@ select * from jobs("type"="insert") where ExecuteType =
"STREAMING";
| LoadStatistic | Job 的统计信息
|
| ErrorMsg | Job 执行的错误信息
|
| JobRuntimeMsg | Job 运行时的一些提示信息
|
-| LagBytes | 数据源端日志（MySQL Binlog / PostgreSQL WAL）的积压字节数，`-1`
表示当前不可用（例如 S3 数据源或全量快照阶段）。**自 4.1.4 版本起**，该列由原来的 `Lag`（单位：秒）改名为
`LagBytes`（单位：字节） |
+| LagBytes | 数据源端日志（MySQL / OceanBase Binlog、PostgreSQL
WAL）的积压字节数，`-1` 表示当前不可用（例如 S3 数据源或全量快照阶段）。**自 4.1.4 版本起**，该列由原来的 `Lag`（单位：秒）改名为
`LagBytes`（单位：字节） |
| LastSourceEventTimestamp | 已提交 Offset 中记录的数据源端最新事件时间戳（Unix 秒），为空表示不可用。**自
4.1.4 版本起新增** |
| LastTaskSuccessTime | 最近一次 Task 成功完成的时间
|
@@ -232,7 +203,7 @@ DROP JOB WHERE jobName = <job_name>;
### Job 通用导入配置参数
-以下参数通过 `CREATE JOB ... PROPERTIES (...)` 配置。除特别说明外，MySQL/PostgreSQL 的 SQL
映射同步和自动建表同步均可使用。
+以下参数通过 `CREATE JOB ... PROPERTIES (...)` 配置。除特别说明外，MySQL、PostgreSQL 和
OceanBase 的持续导入作业均可使用。
| 参数 | 默认值 | 说明 |
| --- | --- | --- |
@@ -240,7 +211,7 @@ DROP JOB WHERE jobName = <job_name>;
| `compute_group` | 当前会话或用户默认计算组 |
仅存算分离模式支持，用于指定作业运行的计算组。显式设置时不能为空，用户必须具有该计算组的 USAGE
权限；未设置且当前会话、用户均没有可用的默认计算组时，创建作业失败。 |
| `session.<variable_name>` | 对应会话变量的默认值 | 仅 TVF 模式支持。为 Job 的 INSERT
任务设置会话变量，例如 `session.insert_max_filter_ratio`。变量名和值必须是 Doris 支持的有效会话变量。 |
-`offset` 作为 Job Property 时不用于设置 MySQL/PostgreSQL 作业的初始位点；创建作业时应在 `FROM
MYSQL`、`FROM POSTGRES` 或 `cdc_stream(...)` 的数据源参数中设置。暂停 CDC 作业后，可以通过 `ALTER JOB
... PROPERTIES ("offset" = '<json_offset>')` 重置位点；MySQL 使用
`{"file":"binlog.000001","pos":"154"}`，PostgreSQL 使用
`{"lsn":"12345678"}`。`ALTER JOB` 仅接受 JSON 形式的精确位点。
+`offset` 作为 Job Property 时不用于设置 CDC 作业的初始位点；创建作业时应在 `FROM MYSQL`、`FROM
POSTGRES`、`FROM OCEANBASE` 或 `cdc_stream(...)` 的数据源参数中设置。暂停 CDC 作业后，可以通过 `ALTER
JOB ... PROPERTIES ("offset" = '<json_offset>')` 重置位点；MySQL 和 OceanBase 使用
`{"file":"binlog.000001","pos":"154"}`，PostgreSQL 使用
`{"lsn":"12345678"}`。`ALTER JOB` 仅接受 JSON 形式的精确位点。
## 使用限制
@@ -256,13 +227,9 @@ DROP JOB WHERE jobName = <job_name>;
DDL 同步**仅适用于[自动建表方式同步](#能力对比)**；[SQL 映射方式同步](#能力对比)不同步任何 DDL——`cdc_stream()`
表函数会强制把 `schema_change_enabled` 设为 `false`。
-- **MySQL 和 PostgreSQL**：仅 `ADD COLUMN` 和 `DROP COLUMN` 会同步。**列类型变更、`RENAME
COLUMN`、主键 / 约束 / 索引 / 分区变更不会同步**——需在 Doris 端手工处理。不同数据源的具体行为和限制详见 [MySQL Schema
Change 同步](./schema-change-mysql.md)与 [PostgreSQL Schema Change
同步](./schema-change-postgresql.md)。
-
-可以通过 Job 属性 `schema_change_enabled` 关闭该能力：
+- **MySQL、PostgreSQL 和 OceanBase**：仅 `ADD COLUMN` 和 `DROP COLUMN`
会同步。**列类型变更、`RENAME COLUMN`、主键 / 约束 / 索引 / 分区变更不会同步**——需在 Doris
端手工处理。不同数据源的具体行为和限制详见
[MySQL](./schema-change-mysql.md)、[PostgreSQL](./schema-change-postgresql.md)和
[OceanBase](./schema-change-oceanbase.md) Schema Change 同步。
-| 参数 | 适用数据源 | 默认值 | 说明 |
-| --- | --- | --- | --- |
-| `schema_change_enabled` | MySQL、PostgreSQL | `true` | 是否自动同步上游的 `ADD COLUMN`
/ `DROP COLUMN`。自 4.1.4 版本起支持 |
+自动建表同步默认启用 Schema Change 同步，目前未提供通过 SQL 关闭该能力的配置参数。
## FAQ
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-way/streaming-job/data-type-mapping-oceanbase.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-way/streaming-job/data-type-mapping-oceanbase.md
new file mode 100644
index 00000000000..a5b27a2e0cb
--- /dev/null
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-way/streaming-job/data-type-mapping-oceanbase.md
@@ -0,0 +1,73 @@
+---
+{
+ "title": "OceanBase 数据类型映射",
+ "language": "zh-CN",
+ "sidebar_label": "数据类型映射",
+ "description": "介绍 OceanBase CDC 自动建表同步中，MySQL 兼容类型如何映射为 Doris 列类型。"
+}
+---
+
+<!-- 知识类型: 参考 / 数据类型映射 -->
+
+OceanBase CDC 持续导入仅支持 MySQL 兼容模式，并复用 MySQL 的类型转换逻辑。下表展示自动建表时 OceanBase 列类型与
Doris 列类型之间的映射。
+
+:::caution 实验性功能
+
+OceanBase CDC 持续导入自 Doris 4.1.4 起作为实验性功能提供。
+
+:::
+
+## JDBC URL 参数归一化
+
+创建 OceanBase Streaming Job 时，如果没有显式指定，Doris 会自动在 `jdbc_url` 中追加以下参数：
+
+| 参数 | 注入值 | 影响 |
+| --- | --- | --- |
+| `tinyInt1isBit` | `false` | `TINYINT(1)` 按 `TINYINT` 读取（`1` / `0`），而不是按
`BOOLEAN` 读取（`true` / `false`）。 |
+| `yearIsDateType` | `false` | `YEAR` 按整数年份读取，而不是按日期读取。 |
+| `useUnicode` | `true` | 使用 Unicode 编码。 |
+| `characterEncoding` | `utf-8` | 使用 UTF-8 字符集。 |
+
+如果在 `jdbc_url` 中显式设置了上述参数，Doris 会保留用户配置的值。
+
+## OceanBase 到 Doris
+
+| OceanBase 类型（MySQL 兼容模式） | Doris 类型 | 备注 |
+| --- | --- | --- |
+| `BOOLEAN` / `TINYINT(1)` | `TINYINT` | 默认取值为 `1` / `0`；可通过
`tinyInt1isBit=true` 改变 JDBC 读取行为。 |
+| `TINYINT` | `TINYINT` | `UNSIGNED` → `SMALLINT` |
+| `SMALLINT` | `SMALLINT` | `UNSIGNED` → `INT` |
+| `MEDIUMINT` | `INT` | `UNSIGNED` → `INT` |
+| `INT` | `INT` | `UNSIGNED` → `BIGINT` |
+| `BIGINT` | `BIGINT` | `UNSIGNED` → `LARGEINT` |
+| `YEAR` | `SMALLINT` | 按整数年份读取；零年（`0000`）保留为 `0`。 |
+| `FLOAT` | `FLOAT` | |
+| `DOUBLE` | `DOUBLE` | |
+| `DECIMAL(p,s)` | `DECIMAL(p,s)` | 超高精度回退为 `STRING`。 |
+| `DATE` | `DATE` | |
+| `DATETIME` | `DATETIME(s)` | 保留微秒精度（0–6）。 |
+| `TIMESTAMP` | `DATETIME(s)` | 按 server 时区归一。 |
+| `TIME` | `STRING` | 以字符串存储，如 `12:34:56.000000`。 |
+| `CHAR` | `CHAR` | |
+| `VARCHAR` | `VARCHAR` | |
+| `TINYTEXT` / `TEXT` / `MEDIUMTEXT` / `LONGTEXT` | `STRING` | |
+| `BINARY` / `VARBINARY` / `TINYBLOB` / `BLOB` / `MEDIUMBLOB` / `LONGBLOB` |
`STRING` | Base64 编码字符串。 |
+| `BIT(1)` | `BOOLEAN` | |
+| `BIT(n>1)` | `STRING` | Base64 编码字符串。 |
+| `JSON` | `STRING` | 以 JSON 文本存储。 |
+| `ENUM` | `STRING` | 解析为标签值。 |
+| `SET` | `STRING` | 解析为逗号分隔的标签。 |
+| 空间类型（`GEOMETRY`、`POINT` 等）及其他类型 | 不支持 | 含此类列的表自动建表会失败；可通过
`table.<table_name>.exclude_columns` 排除非主键列。 |
+
+## 注意事项
+
+- 类型映射以 OceanBase 通过 MySQL Connector/J 返回的元数据为准。
+- 不支持的类型不会自动回退为任意 Doris 类型；创建正式作业前应先验证目标表结构。
+- `TIMESTAMP` 会受源端时区和 JDBC URL 中 `serverTimezone` 的影响，跨时区部署时应显式设置并验证时间值。
+- 主键列不能通过 `table.<table_name>.exclude_columns` 排除。
+
+## 相关文档
+
+- [OceanBase CDC 自动建表同步](./continuous-load-oceanbase-database.md)
+- [OceanBase Schema Change 同步](./schema-change-oceanbase.md)
+- [持续导入概览](./continuous-load-overview.md)
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-way/streaming-job/schema-change-mysql.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-way/streaming-job/schema-change-mysql.md
index 821c80ca09d..0f1aa2d269e 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-way/streaming-job/schema-change-mysql.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-way/streaming-job/schema-change-mysql.md
@@ -40,7 +40,7 @@ MySQL Schema Change 同步自 Doris 4.1.4 起支持。
- `FIRST` 和 `AFTER` 指定的列位置不会同步到 Doris。新增列会追加到 Doris 表的现有列之后。
- `CHANGE COLUMN`、`MODIFY COLUMN`、`RENAME COLUMN`、DEFAULT 变更以及 `NULL` / `NOT
NULL` 约束变更均不会自动同步。执行这些操作前，需要暂停持续导入作业并手动修改 Doris 目标表，确认两端结构兼容后再恢复作业。
- 主键、索引、分区、表名以及其他表级结构变更不会自动同步。
-- 可以通过 Job 属性 `schema_change_enabled`（默认 `true`，自 4.1.4 版本起支持）关闭 Schema Change
自动同步。`cdc_stream()` 表函数（SQL 映射同步）会强制把该属性设为 `false`。
+- 自动建表同步默认启用 Schema Change 同步，目前未提供通过 SQL 关闭该能力的配置参数。`cdc_stream()` 表函数（SQL
映射同步）会在内部关闭 Schema Change 同步。
## 相关文档
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-way/streaming-job/schema-change-oceanbase.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-way/streaming-job/schema-change-oceanbase.md
new file mode 100644
index 00000000000..0dbe05795c3
--- /dev/null
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-way/streaming-job/schema-change-oceanbase.md
@@ -0,0 +1,76 @@
+---
+{
+ "title": "OceanBase Schema Change 同步",
+ "language": "zh-CN",
+ "sidebar_label": "Schema Change 同步",
+ "description": "介绍 OceanBase CDC 自动建表同步支持的 Schema Change 类型、同步行为和限制。",
+ "keywords": [
+ "OceanBase Schema Change",
+ "OceanBase CDC",
+ "自动建表同步",
+ "持续导入",
+ "ADD COLUMN",
+ "DROP COLUMN"
+ ]
+}
+---
+
+<!-- 知识类型: 概念说明 -->
+<!-- 适用场景: OceanBase 自动建表同步期间的上游表结构变更 -->
+
+OceanBase Schema Change 同步用于在持续导入期间，将上游 OceanBase 表的列结构变更自动应用到 Doris
目标表。该能力仅适用于 [OceanBase CDC 自动建表同步](./continuous-load-oceanbase-database.md)。
+
+:::caution 实验性功能
+
+OceanBase Schema Change 同步自 Doris 4.1.4 起作为实验性功能提供，仅支持 MySQL 兼容模式。
+
+:::
+
+OceanBase 复用 MySQL CDC 的 Schema Change 处理逻辑，支持范围和同步行为与 MySQL 一致。
+
+## 支持的 Schema Change
+
+| OceanBase 操作 | Doris 行为 |
+| --- | --- |
+| `ADD COLUMN` | 新增同名列，类型遵循 [OceanBase
数据类型映射](./data-type-mapping-oceanbase.md)，并复制列注释。不复制 DEFAULT 和 `NOT NULL`
约束，也不回填历史数据；后续数据使用 OceanBase 写入 Binlog 的实际值。 |
+| `DROP COLUMN` | 删除同名列。 |
+
+## 注意事项
+
+- 如果新增列已存在或待删除列不存在，Doris 会跳过对应操作，避免作业因重试失败。
+- `FIRST` 和 `AFTER` 指定的列位置不会同步到 Doris；新增列会追加到 Doris 表现有列之后。
+- `CHANGE COLUMN`、`MODIFY COLUMN`、`RENAME COLUMN`、DEFAULT 变更以及 `NULL` / `NOT
NULL` 约束变更不会自动同步。
+- 主键、索引、分区、表名以及其他表级结构变更不会自动同步。
+- 执行不支持的结构变更前，应暂停持续导入作业，手动修改 Doris 目标表并确认两端结构兼容，然后恢复作业。
+- 自动建表同步默认启用 Schema Change 同步，目前未提供通过 SQL 关闭该能力的配置参数。
+
+## 示例
+
+在 OceanBase 源表新增列：
+
+```sql
+ALTER TABLE source_db.users ADD COLUMN city VARCHAR(50);
+INSERT INTO source_db.users VALUES (2, 'Alice', 'Hangzhou');
+```
+
+作业处理完增量数据后，Doris 目标表会增加 `city` 列：
+
+```sql
+DESC target_db.users;
+```
+
+```text
++-------+--------------+------+-------+---------+-------+
+| Field | Type | Null | Key | Default | Extra |
++-------+--------------+------+-------+---------+-------+
+| id | int | No | true | NULL | |
+| name | varchar(100) | Yes | false | NULL | NONE |
+| city | varchar(50) | Yes | false | NULL | NONE |
++-------+--------------+------+-------+---------+-------+
+```
+
+## 相关文档
+
+- [OceanBase CDC 自动建表同步](./continuous-load-oceanbase-database.md)
+- [OceanBase 数据类型映射](./data-type-mapping-oceanbase.md)
+- [持续导入概览](./continuous-load-overview.md)
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-way/streaming-job/schema-change-postgresql.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-way/streaming-job/schema-change-postgresql.md
index 867e5eeabc9..ba64fe29789 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-way/streaming-job/schema-change-postgresql.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/import-way/streaming-job/schema-change-postgresql.md
@@ -41,7 +41,7 @@ PostgreSQL Schema Change 同步自 Doris 4.1.0 起支持。
- 如果新增列已存在或待删除列不存在，Doris 会跳过对应操作，避免作业因重试失败。
- 如果一次表结构变更中同时包含新增列和删除列，Doris 会将其视为潜在的列重命名，不会自动修改目标表，以避免误删数据。
- 列重命名、列类型变更、DEFAULT 变更以及 `NULL` / `NOT NULL`
约束变更均不会自动同步。执行这些操作时，需要暂停持续导入作业并手动修改 Doris 目标表，确认两端结构兼容后再恢复作业。
-- 可以通过 Job 属性 `schema_change_enabled`（默认 `true`，自 4.1.4 版本起支持）关闭 Schema Change
自动同步。`cdc_stream()` 表函数（SQL 映射同步）会强制把该属性设为 `false`。
+- 自动建表同步默认启用 Schema Change 同步，目前未提供通过 SQL 关闭该能力的配置参数。`cdc_stream()` 表函数（SQL
映射同步）会在内部关闭 Schema Change 同步。
:::caution 版本行为变更（4.1.4）
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x.json
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x.json
index e609218ba19..51507339ffd 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x.json
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x.json
@@ -723,6 +723,10 @@
"message": "优化技术原理",
"description": "The label for category Optimization Technology Principles
in sidebar docs"
},
+ "sidebar.docs.category.OceanBase (Experimental)": {
+ "message": "OceanBase（实验性）",
+ "description": "The label for category OceanBase (Experimental) in sidebar
docs"
+ },
"sidebar.docs.category.Paimon Catalog": {
"message": "Paimon Catalog",
"description": "The label for category Paimon Catalog in sidebar docs"
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/import-way/streaming-job/continuous-load-oceanbase-database.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/import-way/streaming-job/continuous-load-oceanbase-database.md
new file mode 100644
index 00000000000..a92fd8252da
--- /dev/null
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/import-way/streaming-job/continuous-load-oceanbase-database.md
@@ -0,0 +1,205 @@
+---
+{
+ "title": "OceanBase CDC 自动建表同步",
+ "language": "zh-CN",
+ "sidebar_label": "自动建表同步",
+ "description": "介绍如何通过 Doris Streaming Job 将 OceanBase MySQL
兼容模式下主键表的全量与增量数据持续同步到 Doris。",
+ "keywords": [
+ "OceanBase 自动建表同步",
+ "OceanBase CDC",
+ "OBBinlog",
+ "Doris Streaming Job",
+ "持续导入",
+ "全量加增量同步",
+ "自动建表"
+ ]
+}
+---
+
+<!-- 知识类型: 操作步骤 + 配置参数 -->
+<!-- 适用场景: OceanBase MySQL 兼容模式整库镜像同步到 Doris -->
+
+OceanBase CDC 自动建表同步通过 `FROM OCEANBASE (...) TO DATABASE (...)` 实现。Doris 从
OBBinlog 服务读取 OceanBase 的全量和增量数据，并根据上游表结构自动创建 Doris 主键表。可以通过 `include_tables`
同步一张、多张或全部表。
+
+:::caution 实验性功能
+
+OceanBase CDC 持续导入自 Doris 4.1.4 起作为实验性功能提供。目前仅支持 OceanBase 的 MySQL
兼容模式和自动建表同步，不支持 Oracle 兼容模式与 SQL 映射同步。
+
+:::
+
+### 适用场景
+
+- 将 OceanBase 中的一组表或整个数据库镜像到 Doris。
+- 由 Doris 根据上游表结构和主键自动创建目标表。
+- 需要先完成全量初始化，再持续同步增量变更。
+- 只需要目标表重命名或列裁剪，不需要 SQL 表达式、行过滤或数据转换。
+
+### 能力与限制
+
+| 项目 | 说明 |
+| --- | --- |
+| 兼容模式 | 仅支持 OceanBase MySQL 兼容模式 |
+| 同步方式 | 仅支持自动建表同步，不支持 SQL 映射同步 |
+| 一致性语义 | at-least-once |
+| 表类型 | 上游表必须有主键；自动创建的 Doris 表为主键模型表（Unique Key） |
+| 权限要求 | 需要 Load 权限；目标表不存在时还需要 Create 权限 |
+| Schema Change | 支持同步 `ADD COLUMN` 和 `DROP COLUMN`，详见 [Schema Change
同步](./schema-change-oceanbase.md) |
+| 数据类型 | 复用 MySQL 兼容类型映射，详见 [数据类型映射](./data-type-mapping-oceanbase.md) |
+
+## 前置准备
+
+创建作业前，请确认：
+
+1. OceanBase 运行在 MySQL 兼容模式。Doris 创建作业时会执行 `SHOW VARIABLES LIKE
'ob_compatibility_mode'` 进行校验。
+2. OBBinlog 服务已部署并可用，通过其 MySQL 协议地址执行 `SHOW MASTER STATUS` 能返回有效的 Binlog
文件名和位点。
+3. Doris FE、BE 与 CDC Client 均可访问 OBBinlog 服务。
+4. 已准备兼容的 MySQL Connector/J 驱动；`jdbc_url` 必须以 `jdbc:mysql://` 开头。
+5. 源端账号可以读取待同步表、表结构和 Binlog。
+6. 待同步的上游表具有主键。
+
+## 快速上手
+
+### 第一步：创建导入作业
+
+以下示例同步 `source_db` 中的 `users` 和 `orders` 表：
+
+```sql
+CREATE JOB oceanbase_db_sync
+ON STREAMING
+FROM OCEANBASE (
+ "jdbc_url" = "jdbc:mysql://127.0.0.1:2883",
+ "driver_url" = "mysql-connector-j-8.4.0.jar",
+ "driver_class" = "com.mysql.cj.jdbc.Driver",
+ "user" = "root@test",
+ "password" = "123456",
+ "database" = "source_db",
+ "include_tables" = "users,orders",
+ "offset" = "initial"
+)
+TO DATABASE target_db (
+ "table.create.properties.replication_num" = "1"
+);
+```
+
+- `jdbc_url` 应指向 OBBinlog 服务的 MySQL 协议端口，具体端口以实际部署为准。
+- `offset = "initial"` 表示先同步存量数据，再持续同步 Binlog 增量。
+- `include_tables` 未设置时，同步 `database` 中所有符合要求的表。
+- 单 BE 部署需要将 `replication_num` 设为 `1`；生产环境请按集群规模设置副本数。
+
+### 第二步：查看导入状态
+
+```sql
+SELECT Name, Status, CurrentOffset, ErrorMsg
+FROM jobs("type" = "insert")
+WHERE Name = "oceanbase_db_sync";
+```
+
+作业正常运行时，`Status` 为 `RUNNING`：
+
+```text
++-------------------+---------+------------------------------------------------+----------+
+| Name | Status | CurrentOffset
| ErrorMsg |
++-------------------+---------+------------------------------------------------+----------+
+| oceanbase_db_sync | RUNNING | {"file":"binlog.000001","pos":"154", ...} |
NULL |
++-------------------+---------+------------------------------------------------+----------+
+```
+
+### 第三步：验证增量同步
+
+在 OceanBase 源表执行 `INSERT`、`UPDATE` 或 `DELETE` 后，查询对应 Doris 表，确认变更已同步：
+
+```sql
+SELECT * FROM target_db.users ORDER BY id;
+```
+
+更多暂停、恢复、删除和 Task 查询操作请参见[持续导入概览](./continuous-load-overview.md#通用操作)。
+
+## 数据源参数
+
+| 参数 | 是否必填 | 默认值 | 说明 |
+| --- | --- | --- | --- |
+| `jdbc_url` | 是 | - | OBBinlog 服务的 JDBC 连接串，必须以 `jdbc:mysql://` 开头。 |
+| `driver_url` | 是 | - | MySQL Connector/J 驱动 jar 包路径，支持文件名、本地绝对路径或 HTTP URL。 |
+| `driver_class` | 是 | - | MySQL JDBC 驱动类名，例如 `com.mysql.cj.jdbc.Driver`。 |
+| `user` | 是 | - | OceanBase 用户名；租户信息按 OceanBase 的用户名格式填写。 |
+| `password` | 是 | - | OceanBase 用户密码。 |
+| `database` | 是 | - | OceanBase 数据库名。 |
+| `include_tables` | 否 | - | 要同步的表名，多个表用逗号分隔；不设置时同步数据库中的全部表。 |
+| `exclude_tables` | 否 | - | 不同步的表名，多个表用逗号分隔；仅在未设置 `include_tables` 时生效。 |
+| `table.<table_name>.target_table` | 否 | 源表名 | 为指定源表设置 Doris 目标表名。 |
+| `table.<table_name>.exclude_columns` | 否 | - |
排除指定源表中的非主键列，多个列用逗号分隔。列必须存在，且不能排除主键列。 |
+| `offset` | 否 | `latest` | `initial`：全量 +
增量；`snapshot`：仅全量；`earliest`：从当前可用的最早 Binlog 位点开始；`latest`：仅同步作业启动后的增量；也可使用
`{"file":"binlog.000001","pos":"154"}` 形式的精确位点。 |
+| `snapshot_split_size` | 否 | `40960` | 全量阶段每个 split 包含的行数，必须为正整数。 |
+| `snapshot_parallelism` | 否 | `1` | 全量阶段单个 Task 最多并行调度的 split 数，必须为正整数。 |
+| `skip_snapshot_backfill` | 否 | `true` | 是否跳过快照期间的 Binlog 回填。自动建表同步采用
at-least-once 语义。 |
+| `server_id` | 否 | 自动生成 | CDC Reader 的 server ID，可设置单值（如 `5400`）或闭区间（如
`5400-5408`）；区间内 ID 数量不得小于 `snapshot_parallelism`。 |
+| `ssl_mode` | 否 | `disable` | SSL 模式，可选值为 `disable`、`require`、`verify-ca`。 |
+| `ssl_rootcert` | 条件必填 | - | `ssl_mode` 为 `verify-ca` 时必填，格式为
`FILE:<file_name>`；需先通过 [CREATE
FILE](../../../../sql-manual/sql-statements/security/CREATE-FILE.md) 上传。 |
+
+不支持 `schema`、`slot_name` 和 `publication_name` 参数。指定这些参数时，作业创建失败。
+
+## 参考手册
+
+### 导入命令
+
+```sql
+CREATE JOB <job_name>
+[job_properties]
+ON STREAMING
+[COMMENT <comment>]
+FROM OCEANBASE (
+ [source_properties]
+)
+TO DATABASE <target_db> (
+ [target_properties]
+);
+```
+
+| 模块 | 说明 |
+| --- | --- |
+| `job_name` | 作业名称。 |
+| `job_properties` | Job 通用参数，例如 `max_interval`。 |
+| `comment` | 作业备注。 |
+| `source_properties` | OceanBase 数据源参数。 |
+| `target_properties` | Doris 目标库参数。 |
+
+### Doris 目标库参数
+
+| 参数 | 默认值 | 说明 |
+| --- | --- | --- |
+| `table.create.properties.*` | - | 自动建表时附加的表属性，例如
`table.create.properties.replication_num`。 |
+| `load.strict_mode` | `false` | 是否为 Stream Load 开启严格模式。 |
+| `load.max_filter_ratio` | `0` | 采样窗口内允许的最大过滤率，范围为 `[0, 1]`；超过该值时作业暂停。 |
+
+## 注意事项与最佳实践
+
+- 生产作业建议先用少量表验证 OBBinlog 连通性、类型映射和增量延迟，再扩大同步范围。
+- 使用 `include_tables` 明确限定同步范围，避免数据库中新增的无关表进入作业。
+- 对不支持的列类型，可通过 `table.<table_name>.exclude_columns` 排除；不能排除主键列。
+- 修改不受支持的表结构前，先暂停作业，在 Doris 端完成兼容变更后再恢复。
+- 定期检查 `CurrentOffset`、`LagBytes` 和 `ErrorMsg`，确认作业持续推进且没有被自动暂停。
+
+## FAQ
+
+**Q1：是否支持 OceanBase Oracle 兼容模式？**
+
+不支持。创建作业时 Doris 会检查 `ob_compatibility_mode`，非 MySQL 兼容模式会直接拒绝创建。
+
+**Q2：是否支持 SQL 映射同步？**
+
+不支持。OceanBase 当前仅支持 `FROM OCEANBASE (...) TO DATABASE (...)` 自动建表同步。
+
+**Q3：如何只同步作业启动后的增量数据？**
+
+将 `offset` 设置为 `latest`。在作业进入 `RUNNING` 后再写入的数据会被同步，已有数据不会执行快照导入。
+
+**Q4：目标表已存在时会被覆盖吗？**
+
+不会。自动建表阶段会跳过已存在的目标表；请确保其主键和列类型与源表兼容。
+
+## 相关文档
+
+- [持续导入概览](./continuous-load-overview.md)
+- [OceanBase Schema Change 同步](./schema-change-oceanbase.md)
+- [OceanBase 数据类型映射](./data-type-mapping-oceanbase.md)
+- [CREATE STREAMING
JOB](../../../../sql-manual/sql-statements/job/CREATE-STREAMING-JOB.md)
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/import-way/streaming-job/continuous-load-overview.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/import-way/streaming-job/continuous-load-overview.md
index 1442e64d9fb..6ff3e88c38a 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/import-way/streaming-job/continuous-load-overview.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/import-way/streaming-job/continuous-load-overview.md
@@ -3,12 +3,13 @@
"title": "持续导入概览",
"language": "zh-CN",
"sidebar_label": "概览",
- "description": "了解 Doris Streaming Job 持续导入：支持的数据源、SQL
映射与自动建表同步选型、作业状态机及通用运维操作。",
+ "description": "了解 Doris Streaming Job 对 MySQL、PostgreSQL、OceanBase 和 S3
的持续导入能力、同步方式选型、作业状态机及通用运维操作。",
"keywords": [
"Doris 持续导入",
"Streaming Job",
"MySQL 实时同步",
"PostgreSQL 实时同步",
+ "OceanBase 实时同步",
"S3 持续导入",
"SQL 映射同步",
"自动建表同步",
@@ -44,41 +45,10 @@ Doris 支持通过 **Streaming Job** 的方式，从多种数据源持续导入
| :--------- | :---------------- |
:-------------------------------------------------------------------- |
:-------------------------------------------------------------------------- |
:----------------------------------------------------------------------------------------------------------------------------------------
|
| MySQL | 5.6、5.7、8.0.x | [MySQL CDC SQL
映射同步](./continuous-load-mysql-table.md) | [MySQL CDC
自动建表同步](./continuous-load-mysql-database.md) | [Amazon RDS
MySQL](./prerequisites/amazon-rds-mysql.md) · [Amazon Aurora
MySQL](./prerequisites/amazon-aurora-mysql.md) |
| PostgreSQL | 14、15、16、17 | [PostgreSQL CDC SQL
映射同步](./continuous-load-postgresql-table.md) | [PostgreSQL CDC
自动建表同步](./continuous-load-postgresql-database.md) | [Amazon RDS
PostgreSQL](./prerequisites/amazon-rds-postgresql.md) · [Amazon Aurora
PostgreSQL](./prerequisites/amazon-aurora-postgresql.md) |
-| OceanBase | MySQL 兼容模式 | -
| 支持（自 4.1.4 版本起），语法见下方【OceanBase 数据源】
| -
|
+| OceanBase | MySQL 兼容模式 | -
| [OceanBase CDC
自动建表同步](./continuous-load-oceanbase-database.md)（自 4.1.4 版本起） | -
|
| S3 | - | [S3 持续导入](./continuous-load-s3.md)
| -
| -
|
-上游列类型如何映射为 Doris 类型，见 [MySQL](./data-type-mapping-mysql.md) /
[PostgreSQL](./data-type-mapping-postgresql.md) 数据类型映射。OceanBase 复用 MySQL 的类型映射。
-
-### OceanBase 数据源
-
-> 自 4.1.4 版本开始支持。
-
-OceanBase 作为持续导入的 CDC 数据源，使用 `FROM OCEANBASE (...)` 子句，属性与 MySQL 数据源一致：
-
-```sql
-CREATE JOB oceanbase_sync ON STREAMING
-FROM OCEANBASE (
- "jdbc_url" = "jdbc:mysql://<host>:<port>",
- "driver_url" = "<driver_jar_url>",
- "driver_class" = "com.mysql.cj.jdbc.Driver",
- "user" = "<user>",
- "password" = "<password>",
- "database" = "<ob_database>",
- "include_tables" = "t1,t2",
- "offset" = "initial"
-)
-TO DATABASE <doris_db> (
- "table.create.properties.replication_num" = "1"
-);
-```
-
-使用限制：
-
-- `jdbc_url` 必须以 `jdbc:mysql://` 开头，否则报错 `OceanBase jdbc_url must start with
'jdbc:mysql://'`；
-- 只支持 OceanBase 的 **MySQL 兼容模式**。作业创建时会执行 `SHOW VARIABLES LIKE
'ob_compatibility_mode'` 探测；Oracle 兼容模式会报错 `OceanBase Oracle compatibility mode
is not supported for streaming jobs`；
-- 不支持 `schema`、`slot_name`、`publication_name` 属性，指定后会报错 `Property '<key>' is
not supported for OceanBase`；
-- `database` 为必填项；
-- `jdbc_url` 的参数归一化规则与 MySQL 一致，详见
[数据类型映射](./data-type-mapping-mysql.md#jdbc-url-参数归一化)。
+上游列类型如何映射为 Doris 类型，见
[MySQL](./data-type-mapping-mysql.md)、[PostgreSQL](./data-type-mapping-postgresql.md)和
[OceanBase](./data-type-mapping-oceanbase.md) 数据类型映射。
## 如何选择同步方式
@@ -103,6 +73,7 @@ SQL 映射同步和自动建表同步是两种**实现机制完全不同**的持
- **需要对数据做 SQL 加工，或对精确一次语义有严格要求** → 选 **SQL 映射同步**
- **希望 Doris 自动建表、一次配置同步一组表** → 选 **自动建表同步**
+- **数据源是 OceanBase** → 目前仅支持 MySQL 兼容模式下的自动建表同步
- **数据源是 S3 对象存储** → 只支持 SQL 映射同步（S3 TVF 方式）
## 作业状态流转
@@ -165,7 +136,7 @@ select * from jobs("type"="insert") where ExecuteType =
"STREAMING";
| LoadStatistic | Job 的统计信息
|
| ErrorMsg | Job 执行的错误信息
|
| JobRuntimeMsg | Job 运行时的一些提示信息
|
-| LagBytes | 数据源端日志（MySQL Binlog / PostgreSQL WAL）的积压字节数，`-1`
表示当前不可用（例如 S3 数据源或全量快照阶段）。**自 4.1.4 版本起**，该列由原来的 `Lag`（单位：秒）改名为
`LagBytes`（单位：字节） |
+| LagBytes | 数据源端日志（MySQL / OceanBase Binlog、PostgreSQL
WAL）的积压字节数，`-1` 表示当前不可用（例如 S3 数据源或全量快照阶段）。**自 4.1.4 版本起**，该列由原来的 `Lag`（单位：秒）改名为
`LagBytes`（单位：字节） |
| LastSourceEventTimestamp | 已提交 Offset 中记录的数据源端最新事件时间戳（Unix 秒），为空表示不可用。**自
4.1.4 版本起新增** |
| LastTaskSuccessTime | 最近一次 Task 成功完成的时间
|
@@ -252,16 +223,13 @@ DDL 同步**仅适用于自动建表同步**；SQL 映射（TVF）不同步任
- **PostgreSQL**（4.1 起支持）：仅 `ADD COLUMN` 和 `DROP COLUMN` 会同步。**列类型变更、`RENAME
COLUMN`、约束 / 索引 / 分区变更不会同步**——需在 Doris 端手工处理。
- **MySQL**（自 4.1.4 起支持）：仅 `ADD COLUMN` 和 `DROP COLUMN` 会同步。**列类型变更、`RENAME
COLUMN`、约束 / 索引 / 分区变更不会同步**——需在 Doris 端手工处理。
+- **OceanBase**（自 4.1.4 起支持）：仅 `ADD COLUMN` 和 `DROP COLUMN`
会同步。**列类型变更、`RENAME COLUMN`、主键 / 约束 / 索引 / 分区变更不会同步**——需在 Doris 端手工处理。
-可以通过 Job 属性 `schema_change_enabled` 关闭该能力：
-
-| 参数 | 适用数据源 | 默认值 | 说明 |
-| --- | --- | --- | --- |
-| `schema_change_enabled` | MySQL、PostgreSQL | `true` | 是否自动同步上游的 `ADD COLUMN`
/ `DROP COLUMN`。自 4.1.4 版本起支持 |
+自动建表同步默认启用 Schema Change 同步，Doris 4.1 目前未提供通过 SQL 关闭该能力的配置参数。
:::caution 版本行为变更（4.1.4）
-- 自 4.1.4 版本起，同步新增列时**不再传递上游列的 `DEFAULT` 值**（MySQL 与 PostgreSQL 均如此）。新增列在
Doris 端不带默认值，历史数据不会回填。
+- 自 4.1.4 版本起，同步新增列时**不再传递上游列的 `DEFAULT` 值**（MySQL、PostgreSQL 和 OceanBase
均如此）。新增列在 Doris 端不带默认值，历史数据不会回填。
- PostgreSQL 的 Schema Change 检测改为基于 Relation 事件驱动：只识别 `ADD COLUMN` 和 `DROP
COLUMN`；同时包含新增和删除列的变更（可能是
`RENAME`）以及列类型变更会被跳过。该能力只在"自动建表同步（at-least-once）"路径上生效，TVF / exactly-once 路径不支持。
:::
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/import-way/streaming-job/data-type-mapping-oceanbase.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/import-way/streaming-job/data-type-mapping-oceanbase.md
new file mode 100644
index 00000000000..a5b27a2e0cb
--- /dev/null
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/import-way/streaming-job/data-type-mapping-oceanbase.md
@@ -0,0 +1,73 @@
+---
+{
+ "title": "OceanBase 数据类型映射",
+ "language": "zh-CN",
+ "sidebar_label": "数据类型映射",
+ "description": "介绍 OceanBase CDC 自动建表同步中，MySQL 兼容类型如何映射为 Doris 列类型。"
+}
+---
+
+<!-- 知识类型: 参考 / 数据类型映射 -->
+
+OceanBase CDC 持续导入仅支持 MySQL 兼容模式，并复用 MySQL 的类型转换逻辑。下表展示自动建表时 OceanBase 列类型与
Doris 列类型之间的映射。
+
+:::caution 实验性功能
+
+OceanBase CDC 持续导入自 Doris 4.1.4 起作为实验性功能提供。
+
+:::
+
+## JDBC URL 参数归一化
+
+创建 OceanBase Streaming Job 时，如果没有显式指定，Doris 会自动在 `jdbc_url` 中追加以下参数：
+
+| 参数 | 注入值 | 影响 |
+| --- | --- | --- |
+| `tinyInt1isBit` | `false` | `TINYINT(1)` 按 `TINYINT` 读取（`1` / `0`），而不是按
`BOOLEAN` 读取（`true` / `false`）。 |
+| `yearIsDateType` | `false` | `YEAR` 按整数年份读取，而不是按日期读取。 |
+| `useUnicode` | `true` | 使用 Unicode 编码。 |
+| `characterEncoding` | `utf-8` | 使用 UTF-8 字符集。 |
+
+如果在 `jdbc_url` 中显式设置了上述参数，Doris 会保留用户配置的值。
+
+## OceanBase 到 Doris
+
+| OceanBase 类型（MySQL 兼容模式） | Doris 类型 | 备注 |
+| --- | --- | --- |
+| `BOOLEAN` / `TINYINT(1)` | `TINYINT` | 默认取值为 `1` / `0`；可通过
`tinyInt1isBit=true` 改变 JDBC 读取行为。 |
+| `TINYINT` | `TINYINT` | `UNSIGNED` → `SMALLINT` |
+| `SMALLINT` | `SMALLINT` | `UNSIGNED` → `INT` |
+| `MEDIUMINT` | `INT` | `UNSIGNED` → `INT` |
+| `INT` | `INT` | `UNSIGNED` → `BIGINT` |
+| `BIGINT` | `BIGINT` | `UNSIGNED` → `LARGEINT` |
+| `YEAR` | `SMALLINT` | 按整数年份读取；零年（`0000`）保留为 `0`。 |
+| `FLOAT` | `FLOAT` | |
+| `DOUBLE` | `DOUBLE` | |
+| `DECIMAL(p,s)` | `DECIMAL(p,s)` | 超高精度回退为 `STRING`。 |
+| `DATE` | `DATE` | |
+| `DATETIME` | `DATETIME(s)` | 保留微秒精度（0–6）。 |
+| `TIMESTAMP` | `DATETIME(s)` | 按 server 时区归一。 |
+| `TIME` | `STRING` | 以字符串存储，如 `12:34:56.000000`。 |
+| `CHAR` | `CHAR` | |
+| `VARCHAR` | `VARCHAR` | |
+| `TINYTEXT` / `TEXT` / `MEDIUMTEXT` / `LONGTEXT` | `STRING` | |
+| `BINARY` / `VARBINARY` / `TINYBLOB` / `BLOB` / `MEDIUMBLOB` / `LONGBLOB` |
`STRING` | Base64 编码字符串。 |
+| `BIT(1)` | `BOOLEAN` | |
+| `BIT(n>1)` | `STRING` | Base64 编码字符串。 |
+| `JSON` | `STRING` | 以 JSON 文本存储。 |
+| `ENUM` | `STRING` | 解析为标签值。 |
+| `SET` | `STRING` | 解析为逗号分隔的标签。 |
+| 空间类型（`GEOMETRY`、`POINT` 等）及其他类型 | 不支持 | 含此类列的表自动建表会失败；可通过
`table.<table_name>.exclude_columns` 排除非主键列。 |
+
+## 注意事项
+
+- 类型映射以 OceanBase 通过 MySQL Connector/J 返回的元数据为准。
+- 不支持的类型不会自动回退为任意 Doris 类型；创建正式作业前应先验证目标表结构。
+- `TIMESTAMP` 会受源端时区和 JDBC URL 中 `serverTimezone` 的影响，跨时区部署时应显式设置并验证时间值。
+- 主键列不能通过 `table.<table_name>.exclude_columns` 排除。
+
+## 相关文档
+
+- [OceanBase CDC 自动建表同步](./continuous-load-oceanbase-database.md)
+- [OceanBase Schema Change 同步](./schema-change-oceanbase.md)
+- [持续导入概览](./continuous-load-overview.md)
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/import-way/streaming-job/schema-change-mysql.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/import-way/streaming-job/schema-change-mysql.md
index 821c80ca09d..e50904e58ef 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/import-way/streaming-job/schema-change-mysql.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/import-way/streaming-job/schema-change-mysql.md
@@ -40,7 +40,7 @@ MySQL Schema Change 同步自 Doris 4.1.4 起支持。
- `FIRST` 和 `AFTER` 指定的列位置不会同步到 Doris。新增列会追加到 Doris 表的现有列之后。
- `CHANGE COLUMN`、`MODIFY COLUMN`、`RENAME COLUMN`、DEFAULT 变更以及 `NULL` / `NOT
NULL` 约束变更均不会自动同步。执行这些操作前，需要暂停持续导入作业并手动修改 Doris 目标表，确认两端结构兼容后再恢复作业。
- 主键、索引、分区、表名以及其他表级结构变更不会自动同步。
-- 可以通过 Job 属性 `schema_change_enabled`（默认 `true`，自 4.1.4 版本起支持）关闭 Schema Change
自动同步。`cdc_stream()` 表函数（SQL 映射同步）会强制把该属性设为 `false`。
+- 自动建表同步默认启用 Schema Change 同步，Doris 4.1 未提供通过 SQL 关闭该能力的配置参数。`cdc_stream()`
表函数（SQL 映射同步）会在内部关闭 Schema Change 同步。
## 相关文档
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/import-way/streaming-job/schema-change-oceanbase.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/import-way/streaming-job/schema-change-oceanbase.md
new file mode 100644
index 00000000000..0dbe05795c3
--- /dev/null
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/import-way/streaming-job/schema-change-oceanbase.md
@@ -0,0 +1,76 @@
+---
+{
+ "title": "OceanBase Schema Change 同步",
+ "language": "zh-CN",
+ "sidebar_label": "Schema Change 同步",
+ "description": "介绍 OceanBase CDC 自动建表同步支持的 Schema Change 类型、同步行为和限制。",
+ "keywords": [
+ "OceanBase Schema Change",
+ "OceanBase CDC",
+ "自动建表同步",
+ "持续导入",
+ "ADD COLUMN",
+ "DROP COLUMN"
+ ]
+}
+---
+
+<!-- 知识类型: 概念说明 -->
+<!-- 适用场景: OceanBase 自动建表同步期间的上游表结构变更 -->
+
+OceanBase Schema Change 同步用于在持续导入期间，将上游 OceanBase 表的列结构变更自动应用到 Doris
目标表。该能力仅适用于 [OceanBase CDC 自动建表同步](./continuous-load-oceanbase-database.md)。
+
+:::caution 实验性功能
+
+OceanBase Schema Change 同步自 Doris 4.1.4 起作为实验性功能提供，仅支持 MySQL 兼容模式。
+
+:::
+
+OceanBase 复用 MySQL CDC 的 Schema Change 处理逻辑，支持范围和同步行为与 MySQL 一致。
+
+## 支持的 Schema Change
+
+| OceanBase 操作 | Doris 行为 |
+| --- | --- |
+| `ADD COLUMN` | 新增同名列，类型遵循 [OceanBase
数据类型映射](./data-type-mapping-oceanbase.md)，并复制列注释。不复制 DEFAULT 和 `NOT NULL`
约束，也不回填历史数据；后续数据使用 OceanBase 写入 Binlog 的实际值。 |
+| `DROP COLUMN` | 删除同名列。 |
+
+## 注意事项
+
+- 如果新增列已存在或待删除列不存在，Doris 会跳过对应操作，避免作业因重试失败。
+- `FIRST` 和 `AFTER` 指定的列位置不会同步到 Doris；新增列会追加到 Doris 表现有列之后。
+- `CHANGE COLUMN`、`MODIFY COLUMN`、`RENAME COLUMN`、DEFAULT 变更以及 `NULL` / `NOT
NULL` 约束变更不会自动同步。
+- 主键、索引、分区、表名以及其他表级结构变更不会自动同步。
+- 执行不支持的结构变更前，应暂停持续导入作业，手动修改 Doris 目标表并确认两端结构兼容，然后恢复作业。
+- 自动建表同步默认启用 Schema Change 同步，目前未提供通过 SQL 关闭该能力的配置参数。
+
+## 示例
+
+在 OceanBase 源表新增列：
+
+```sql
+ALTER TABLE source_db.users ADD COLUMN city VARCHAR(50);
+INSERT INTO source_db.users VALUES (2, 'Alice', 'Hangzhou');
+```
+
+作业处理完增量数据后，Doris 目标表会增加 `city` 列：
+
+```sql
+DESC target_db.users;
+```
+
+```text
++-------+--------------+------+-------+---------+-------+
+| Field | Type | Null | Key | Default | Extra |
++-------+--------------+------+-------+---------+-------+
+| id | int | No | true | NULL | |
+| name | varchar(100) | Yes | false | NULL | NONE |
+| city | varchar(50) | Yes | false | NULL | NONE |
++-------+--------------+------+-------+---------+-------+
+```
+
+## 相关文档
+
+- [OceanBase CDC 自动建表同步](./continuous-load-oceanbase-database.md)
+- [OceanBase 数据类型映射](./data-type-mapping-oceanbase.md)
+- [持续导入概览](./continuous-load-overview.md)
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/import-way/streaming-job/schema-change-postgresql.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/import-way/streaming-job/schema-change-postgresql.md
index 867e5eeabc9..655806c3070 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/import-way/streaming-job/schema-change-postgresql.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/import-way/streaming-job/schema-change-postgresql.md
@@ -41,7 +41,7 @@ PostgreSQL Schema Change 同步自 Doris 4.1.0 起支持。
- 如果新增列已存在或待删除列不存在，Doris 会跳过对应操作，避免作业因重试失败。
- 如果一次表结构变更中同时包含新增列和删除列，Doris 会将其视为潜在的列重命名，不会自动修改目标表，以避免误删数据。
- 列重命名、列类型变更、DEFAULT 变更以及 `NULL` / `NOT NULL`
约束变更均不会自动同步。执行这些操作时，需要暂停持续导入作业并手动修改 Doris 目标表，确认两端结构兼容后再恢复作业。
-- 可以通过 Job 属性 `schema_change_enabled`（默认 `true`，自 4.1.4 版本起支持）关闭 Schema Change
自动同步。`cdc_stream()` 表函数（SQL 映射同步）会强制把该属性设为 `false`。
+- 自动建表同步默认启用 Schema Change 同步，Doris 4.1 未提供通过 SQL 关闭该能力的配置参数。`cdc_stream()`
表函数（SQL 映射同步）会在内部关闭 Schema Change 同步。
:::caution 版本行为变更（4.1.4）
diff --git a/sidebars.ts b/sidebars.ts
index 64ecd7e7ba4..62a6c81019a 100644
--- a/sidebars.ts
+++ b/sidebars.ts
@@ -406,6 +406,15 @@ const sidebars: SidebarsConfig = {
},
],
},
+ {
+ type: 'category',
+ label: 'OceanBase (Experimental)',
+ items: [
+
'data-operate/import/import-way/streaming-job/continuous-load-oceanbase-database',
+
'data-operate/import/import-way/streaming-job/schema-change-oceanbase',
+
'data-operate/import/import-way/streaming-job/data-type-mapping-oceanbase',
+ ],
+ },
'data-operate/import/import-way/streaming-job/continuous-load-s3',
],
},
diff --git
a/versioned_docs/version-4.x/data-operate/import/import-way/streaming-job/continuous-load-oceanbase-database.md
b/versioned_docs/version-4.x/data-operate/import/import-way/streaming-job/continuous-load-oceanbase-database.md
new file mode 100644
index 00000000000..0a8015393a7
--- /dev/null
+++
b/versioned_docs/version-4.x/data-operate/import/import-way/streaming-job/continuous-load-oceanbase-database.md
@@ -0,0 +1,205 @@
+---
+{
+ "title": "OceanBase CDC with Auto Table Creation",
+ "language": "en",
+ "sidebar_label": "Auto Table Creation Sync",
+ "description": "Learn how to continuously sync full and incremental data
from primary-key tables in OceanBase MySQL compatibility mode to Doris through
a Streaming Job.",
+ "keywords": [
+ "OceanBase Auto Table Creation Sync",
+ "OceanBase CDC",
+ "OBBinlog",
+ "Doris Streaming Job",
+ "continuous load",
+ "full and incremental sync",
+ "automatic table creation"
+ ]
+}
+---
+
+<!-- Knowledge type: Procedure + Configuration parameters -->
+<!-- Applicable scenario: Mirror an OceanBase database in MySQL compatibility
mode to Doris -->
+
+OceanBase CDC with Auto Table Creation uses `FROM OCEANBASE (...) TO DATABASE
(...)`. Doris reads full and incremental data through the OBBinlog service and
automatically creates Doris Unique Key tables from the upstream schemas. Use
`include_tables` to sync one table, multiple tables, or all tables in the
database.
+
+:::caution Experimental feature
+
+OceanBase CDC continuous load is available as an experimental feature starting
from Doris 4.1.4. It currently supports only OceanBase MySQL compatibility mode
and Auto Table Creation Sync. Oracle compatibility mode and SQL Mapping Sync
are not supported.
+
+:::
+
+### Applicable Scenarios
+
+- Mirror a group of OceanBase tables or an entire database to Doris.
+- Let Doris create target tables and primary keys from the upstream schemas.
+- Perform an initial full load and then continuously sync incremental changes.
+- Rename target tables or exclude columns without SQL expressions, row
filters, or data transformations.
+
+### Capabilities and Limitations
+
+| Item | Description |
+| --- | --- |
+| Compatibility mode | OceanBase MySQL compatibility mode only |
+| Sync method | Auto Table Creation Sync only; SQL Mapping Sync is not
supported |
+| Consistency semantics | At-least-once |
+| Table type | Upstream tables must have primary keys; automatically created
Doris tables use the Unique Key model |
+| Permissions | Load permission is required; Create permission is also
required when the target table does not exist |
+| Schema Change | Syncs `ADD COLUMN` and `DROP COLUMN`; see [Schema Change
Sync](./schema-change-oceanbase.md) |
+| Data types | Uses MySQL-compatible type conversion; see [Data Type
Mapping](./data-type-mapping-oceanbase.md) |
+
+## Prerequisites
+
+Before creating a job, confirm the following:
+
+1. OceanBase runs in MySQL compatibility mode. Doris validates the mode by
running `SHOW VARIABLES LIKE 'ob_compatibility_mode'` when creating the job.
+2. The OBBinlog service is deployed and available. Running `SHOW MASTER
STATUS` against its MySQL protocol endpoint returns a valid binlog file and
position.
+3. Doris FE, BE, and CDC Client can access the OBBinlog service.
+4. A compatible MySQL Connector/J driver is available, and `jdbc_url` starts
with `jdbc:mysql://`.
+5. The source account can read the tables, schemas, and binlog in the sync
scope.
+6. Every upstream table to be synced has a primary key.
+
+## Quick Start
+
+### Step 1: Create a Load Job
+
+The following example syncs the `users` and `orders` tables in `source_db`:
+
+```sql
+CREATE JOB oceanbase_db_sync
+ON STREAMING
+FROM OCEANBASE (
+ "jdbc_url" = "jdbc:mysql://127.0.0.1:2883",
+ "driver_url" = "mysql-connector-j-8.4.0.jar",
+ "driver_class" = "com.mysql.cj.jdbc.Driver",
+ "user" = "root@test",
+ "password" = "123456",
+ "database" = "source_db",
+ "include_tables" = "users,orders",
+ "offset" = "initial"
+)
+TO DATABASE target_db (
+ "table.create.properties.replication_num" = "1"
+);
+```
+
+- `jdbc_url` points to the MySQL protocol port of the OBBinlog service. Use
the port configured in your deployment.
+- `offset = "initial"` loads existing rows first and then continuously syncs
binlog changes.
+- If `include_tables` is omitted, all eligible tables in `database` are synced.
+- For a single-BE deployment, set `replication_num` to `1`. In production, set
the replica count according to the cluster size.
+
+### Step 2: Check Load Status
+
+```sql
+SELECT Name, Status, CurrentOffset, ErrorMsg
+FROM jobs("type" = "insert")
+WHERE Name = "oceanbase_db_sync";
+```
+
+When the job is running normally, `Status` is `RUNNING`:
+
+```text
++-------------------+---------+-----------------------------------------------+----------+
+| Name | Status | CurrentOffset
| ErrorMsg |
++-------------------+---------+-----------------------------------------------+----------+
+| oceanbase_db_sync | RUNNING | {"file":"binlog.000001","pos":"154", ...} |
NULL |
++-------------------+---------+-----------------------------------------------+----------+
+```
+
+### Step 3: Verify Incremental Sync
+
+After running `INSERT`, `UPDATE`, or `DELETE` against an OceanBase source
table, query the corresponding Doris table and verify that the change has been
synchronized:
+
+```sql
+SELECT * FROM target_db.users ORDER BY id;
+```
+
+For pause, resume, delete, and Task query operations, see [Continuous Load
Overview](./continuous-load-overview.md#common-operations).
+
+## Data Source Parameters
+
+| Parameter | Required | Default | Description |
+| --- | --- | --- | --- |
+| `jdbc_url` | Yes | - | JDBC connection string for the OBBinlog service. It
must start with `jdbc:mysql://`. |
+| `driver_url` | Yes | - | Path to the MySQL Connector/J driver jar. Supports
a file name, local absolute path, or HTTP URL. |
+| `driver_class` | Yes | - | MySQL JDBC driver class, for example,
`com.mysql.cj.jdbc.Driver`. |
+| `user` | Yes | - | OceanBase user name. Include tenant information using the
user name format required by OceanBase. |
+| `password` | Yes | - | OceanBase user password. |
+| `database` | Yes | - | OceanBase database name. |
+| `include_tables` | No | - | Table names to sync, separated by commas. If
omitted, all tables in the database are synced. |
+| `exclude_tables` | No | - | Table names not to sync, separated by commas.
This parameter takes effect only when `include_tables` is not set. |
+| `table.<table_name>.target_table` | No | Source table name | Sets the Doris
target table name for a source table. |
+| `table.<table_name>.exclude_columns` | No | - | Excludes non-key columns
from a source table, separated by commas. Each column must exist and cannot be
a primary key column. |
+| `offset` | No | `latest` | Startup position. `initial`: full and incremental
sync; `snapshot`: full sync only; `earliest`: start at the earliest available
binlog position; `latest`: sync only changes after the job starts. An exact
position such as `{"file":"binlog.000001","pos":"154"}` is also supported. |
+| `snapshot_split_size` | No | `40960` | Number of rows in each split during
the full-sync phase. Must be a positive integer. |
+| `snapshot_parallelism` | No | `1` | Maximum number of splits scheduled
concurrently by one Task during the full-sync phase. Must be a positive
integer. |
+| `skip_snapshot_backfill` | No | `true` | Whether to skip binlog backfill
during the snapshot phase. Auto Table Creation Sync provides at-least-once
semantics. |
+| `server_id` | No | Automatically generated | Server ID of the CDC reader.
Supports a single value such as `5400` or a closed range such as `5400-5408`.
The range must contain at least `snapshot_parallelism` IDs. |
+| `ssl_mode` | No | `disable` | SSL mode. Valid values are `disable`,
`require`, and `verify-ca`. |
+| `ssl_rootcert` | Conditionally required | - | Required when `ssl_mode` is
`verify-ca`. Use the format `FILE:<file_name>` and upload the file first with
[CREATE FILE](../../../../sql-manual/sql-statements/security/CREATE-FILE.md). |
+
+The `schema`, `slot_name`, and `publication_name` parameters are not
supported. Job creation fails if any of them is specified.
+
+## Reference Manual
+
+### Load Statement
+
+```sql
+CREATE JOB <job_name>
+[job_properties]
+ON STREAMING
+[COMMENT <comment>]
+FROM OCEANBASE (
+ [source_properties]
+)
+TO DATABASE <target_db> (
+ [target_properties]
+);
+```
+
+| Module | Description |
+| --- | --- |
+| `job_name` | Job name. |
+| `job_properties` | Common Job parameters such as `max_interval`. |
+| `comment` | Job comment. |
+| `source_properties` | OceanBase data source parameters. |
+| `target_properties` | Doris target database parameters. |
+
+### Doris Target Database Parameters
+
+| Parameter | Default | Description |
+| --- | --- | --- |
+| `table.create.properties.*` | - | Adds table properties when Doris creates a
table, for example, `table.create.properties.replication_num`. |
+| `load.strict_mode` | `false` | Whether to enable strict mode for Stream
Load. |
+| `load.max_filter_ratio` | `0` | Maximum filter ratio allowed in the sampling
window, in the range `[0, 1]`. The job is paused when the ratio exceeds this
value. |
+
+## Considerations and Best Practices
+
+- Before expanding the sync scope in production, use a small set of tables to
verify OBBinlog connectivity, type mappings, and incremental latency.
+- Use `include_tables` to define the sync scope explicitly so that unrelated
tables added later are not included automatically.
+- Exclude unsupported non-key columns with
`table.<table_name>.exclude_columns`. Primary key columns cannot be excluded.
+- Before making an unsupported schema change, pause the job, apply a
compatible change to the Doris table, and then resume the job.
+- Monitor `CurrentOffset`, `LagBytes`, and `ErrorMsg` to verify that the job
continues to make progress and has not been paused automatically.
+
+## FAQ
+
+**Q1: Is OceanBase Oracle compatibility mode supported?**
+
+No. Doris checks `ob_compatibility_mode` during job creation and rejects any
mode other than MySQL compatibility mode.
+
+**Q2: Is SQL Mapping Sync supported?**
+
+No. OceanBase currently supports only `FROM OCEANBASE (...) TO DATABASE (...)`
Auto Table Creation Sync.
+
+**Q3: How do I sync only changes that occur after the job starts?**
+
+Set `offset` to `latest`. Rows that exist before the job reaches `RUNNING` are
not loaded through a snapshot.
+
+**Q4: Is an existing target table overwritten?**
+
+No. Auto table creation skips a target table that already exists. Make sure
its primary key and column types are compatible with the source table.
+
+## Related Documents
+
+- [Continuous Load Overview](./continuous-load-overview.md)
+- [OceanBase Schema Change Sync](./schema-change-oceanbase.md)
+- [OceanBase Data Type Mapping](./data-type-mapping-oceanbase.md)
+- [CREATE STREAMING
JOB](../../../../sql-manual/sql-statements/job/CREATE-STREAMING-JOB.md)
diff --git
a/versioned_docs/version-4.x/data-operate/import/import-way/streaming-job/continuous-load-overview.md
b/versioned_docs/version-4.x/data-operate/import/import-way/streaming-job/continuous-load-overview.md
index 37a698df6b8..ff01f0089c2 100644
---
a/versioned_docs/version-4.x/data-operate/import/import-way/streaming-job/continuous-load-overview.md
+++
b/versioned_docs/version-4.x/data-operate/import/import-way/streaming-job/continuous-load-overview.md
@@ -3,12 +3,13 @@
"title": "Continuous Load Overview",
"language": "en",
"sidebar_label": "Overview",
- "description": "Learn about Doris Streaming Job continuous load: supported
data sources, SQL Mapping vs Auto Table Creation selection, job state machine,
and common operations.",
+ "description": "Learn about Doris Streaming Job continuous load for MySQL,
PostgreSQL, OceanBase, and S3, including sync method selection, job states, and
common operations.",
"keywords": [
"Doris continuous load",
"Streaming Job",
"MySQL real-time sync",
"PostgreSQL real-time sync",
+ "OceanBase real-time sync",
"S3 continuous load",
"SQL Mapping Sync",
"Auto Table Creation Sync",
@@ -44,41 +45,10 @@ Continuous load supports the following data sources and
sync modes:
| :---------- | :----------------- |
:---------------------------------------------------------------- |
:---------------------------------------------------------------------- |
:----------------------------------------------------------------------------------------------------------------------------------------
|
| MySQL | 5.6, 5.7, 8.0.x | [MySQL CDC with SQL
Mapping](./continuous-load-mysql-table.md) | [MySQL CDC with Auto Table
Creation](./continuous-load-mysql-database.md) | [Amazon RDS
MySQL](./prerequisites/amazon-rds-mysql.md) · [Amazon Aurora
MySQL](./prerequisites/amazon-aurora-mysql.md) |
| PostgreSQL | 14, 15, 16, 17 | [PostgreSQL CDC with SQL
Mapping](./continuous-load-postgresql-table.md) | [PostgreSQL CDC with Auto
Table Creation](./continuous-load-postgresql-database.md) | [Amazon RDS
PostgreSQL](./prerequisites/amazon-rds-postgresql.md) · [Amazon Aurora
PostgreSQL](./prerequisites/amazon-aurora-postgresql.md) |
-| OceanBase | MySQL compatibility mode | -
| Supported (since version 4.1.4). For the syntax, see
[OceanBase Data Source](#oceanbase-data-source) | -
|
+| OceanBase | MySQL compatibility mode | -
| [OceanBase CDC with Auto Table
Creation](./continuous-load-oceanbase-database.md) (since version 4.1.4) | -
|
| S3 | - | [S3 Continuous
Load](./continuous-load-s3.md) | -
| -
|
-For how upstream column types map to Doris types, see Data Type Mapping for
[MySQL](./data-type-mapping-mysql.md) and
[PostgreSQL](./data-type-mapping-postgresql.md). OceanBase reuses the MySQL
type mapping.
-
-### OceanBase Data Source
-
-> Supported since version 4.1.4.
-
-To use OceanBase as a CDC data source for continuous load, use the `FROM
OCEANBASE (...)` clause. Its properties are the same as those of the MySQL data
source:
-
-```sql
-CREATE JOB oceanbase_sync ON STREAMING
-FROM OCEANBASE (
- "jdbc_url" = "jdbc:mysql://<host>:<port>",
- "driver_url" = "<driver_jar_url>",
- "driver_class" = "com.mysql.cj.jdbc.Driver",
- "user" = "<user>",
- "password" = "<password>",
- "database" = "<ob_database>",
- "include_tables" = "t1,t2",
- "offset" = "initial"
-)
-TO DATABASE <doris_db> (
- "table.create.properties.replication_num" = "1"
-);
-```
-
-Limitations:
-
-- `jdbc_url` must start with `jdbc:mysql://`, otherwise the job fails with
`OceanBase jdbc_url must start with 'jdbc:mysql://'`.
-- Only the **MySQL compatibility mode** of OceanBase is supported. When the
job is created, Doris runs `SHOW VARIABLES LIKE 'ob_compatibility_mode'` to
detect the mode; the Oracle compatibility mode fails with `OceanBase Oracle
compatibility mode is not supported for streaming jobs`.
-- The `schema`, `slot_name`, and `publication_name` properties are not
supported. Specifying any of them fails with `Property '<key>' is not supported
for OceanBase`.
-- `database` is required.
-- `jdbc_url` parameters are normalized in the same way as for MySQL. See [JDBC
URL Parameter
Normalization](./data-type-mapping-mysql.md#jdbc-url-parameter-normalization).
+For how upstream column types map to Doris types, see Data Type Mapping for
[MySQL](./data-type-mapping-mysql.md),
[PostgreSQL](./data-type-mapping-postgresql.md), and
[OceanBase](./data-type-mapping-oceanbase.md).
## How to Choose a Sync Method
@@ -103,6 +73,7 @@ SQL Mapping Sync and Auto Table Creation Sync are two
continuous load methods wi
- **You need to apply SQL processing to the data, or you have strict
requirements for exactly-once semantics** -> choose **SQL Mapping Sync**
- **You want Doris to create tables automatically and sync a group of tables
with one configuration** -> choose **Auto Table Creation Sync**
+- **The data source is OceanBase** -> currently, only Auto Table Creation Sync
in MySQL compatibility mode is supported
- **The data source is S3 object storage** -> only SQL Mapping Sync is
supported (using the S3 TVF)
## Job State Transitions
@@ -165,7 +136,7 @@ Result columns:
| LoadStatistic | Job statistics
|
| ErrorMsg | Error message of the Job
|
| JobRuntimeMsg | Runtime hints of the Job
|
-| LagBytes | Number of backlog bytes in the source log (MySQL binlog
/ PostgreSQL WAL). `-1` means the value is currently unavailable, for example
for an S3 data source or during the full snapshot phase. **Since version
4.1.4**, this column replaces the former `Lag` column (in seconds) and is
reported in bytes |
+| LagBytes | Number of backlog bytes in the source log (MySQL /
OceanBase binlog or PostgreSQL WAL). `-1` means the value is currently
unavailable, for example for an S3 data source or during the full snapshot
phase. **Since version 4.1.4**, this column replaces the former `Lag` column
(in seconds) and is reported in bytes |
| LastSourceEventTimestamp | Timestamp (in Unix seconds) of the latest source
event recorded in the committed offset. Empty when unavailable. **Added in
version 4.1.4** |
| LastTaskSuccessTime | Time when the most recent Task completed successfully
|
@@ -252,16 +223,13 @@ DDL sync applies **only to Auto Table Creation Sync**;
SQL Mapping (TVF) does no
- **PostgreSQL** (supported since 4.1): only `ADD COLUMN` and `DROP COLUMN`
are synced. **Column type changes, `RENAME COLUMN`, and constraint / index /
partition changes are NOT synced** — apply them manually in Doris.
- **MySQL** (supported since 4.1.4): only `ADD COLUMN` and `DROP COLUMN` are
synced. **Column type changes, `RENAME COLUMN`, and constraint / index /
partition changes are NOT synced** — apply them manually in Doris.
+- **OceanBase** (supported since 4.1.4): only `ADD COLUMN` and `DROP COLUMN`
are synced. **Column type changes, `RENAME COLUMN`, and primary key /
constraint / index / partition changes are NOT synced** — apply them manually
in Doris.
-You can turn this capability off with the Job property `schema_change_enabled`:
-
-| Parameter | Applicable data sources | Default | Description |
-| --- | --- | --- | --- |
-| `schema_change_enabled` | MySQL, PostgreSQL | `true` | Whether to
automatically sync upstream `ADD COLUMN` / `DROP COLUMN`. Supported since
version 4.1.4 |
+Auto Table Creation Sync enables Schema Change Sync by default. Doris 4.1
currently does not provide a SQL property to disable it.
:::caution Behavior change (4.1.4)
-- Starting from version 4.1.4, an added column **no longer carries the
`DEFAULT` value of the upstream column** (for both MySQL and PostgreSQL). The
new column has no default value in Doris, and historical rows are not
backfilled.
+- Starting from version 4.1.4, an added column **no longer carries the
`DEFAULT` value of the upstream column** (for MySQL, PostgreSQL, and
OceanBase). The new column has no default value in Doris, and historical rows
are not backfilled.
- PostgreSQL schema change detection is now driven by Relation events: only
`ADD COLUMN` and `DROP COLUMN` are recognized; a change that both adds and
drops columns (possibly a `RENAME`) is skipped, as are column type changes.
This capability applies only to the Auto Table Creation Sync (at-least-once)
path; the TVF / exactly-once path does not support it.
:::
diff --git
a/versioned_docs/version-4.x/data-operate/import/import-way/streaming-job/data-type-mapping-oceanbase.md
b/versioned_docs/version-4.x/data-operate/import/import-way/streaming-job/data-type-mapping-oceanbase.md
new file mode 100644
index 00000000000..16ea4b15cf2
--- /dev/null
+++
b/versioned_docs/version-4.x/data-operate/import/import-way/streaming-job/data-type-mapping-oceanbase.md
@@ -0,0 +1,73 @@
+---
+{
+ "title": "OceanBase Data Type Mapping",
+ "language": "en",
+ "sidebar_label": "Data Type Mapping",
+ "description": "Learn how MySQL-compatible OceanBase column types map to
Doris column types during CDC Auto Table Creation Sync."
+}
+---
+
+<!-- Knowledge type: Reference / data type mapping -->
+
+OceanBase CDC continuous load supports only MySQL compatibility mode and uses
the MySQL type conversion path. The following table shows how OceanBase column
types map to Doris column types during automatic table creation.
+
+:::caution Experimental feature
+
+OceanBase CDC continuous load is available as an experimental feature starting
from Doris 4.1.4.
+
+:::
+
+## JDBC URL Parameter Normalization
+
+When you create an OceanBase Streaming Job, Doris automatically appends the
following parameters to `jdbc_url` unless you set them explicitly:
+
+| Parameter | Injected Value | Effect |
+| --- | --- | --- |
+| `tinyInt1isBit` | `false` | Reads `TINYINT(1)` as `TINYINT` (`1` / `0`)
instead of `BOOLEAN` (`true` / `false`). |
+| `yearIsDateType` | `false` | Reads `YEAR` as an integer year instead of a
date. |
+| `useUnicode` | `true` | Uses Unicode encoding. |
+| `characterEncoding` | `utf-8` | Uses UTF-8 as the character set. |
+
+If any of these parameters is set explicitly in `jdbc_url`, Doris keeps the
configured value.
+
+## OceanBase to Doris
+
+| OceanBase Type (MySQL compatibility mode) | Doris Type | Notes |
+| --- | --- | --- |
+| `BOOLEAN` / `TINYINT(1)` | `TINYINT` | Values are `1` / `0` by default. Set
`tinyInt1isBit=true` to change the JDBC read behavior. |
+| `TINYINT` | `TINYINT` | `UNSIGNED` → `SMALLINT` |
+| `SMALLINT` | `SMALLINT` | `UNSIGNED` → `INT` |
+| `MEDIUMINT` | `INT` | `UNSIGNED` → `INT` |
+| `INT` | `INT` | `UNSIGNED` → `BIGINT` |
+| `BIGINT` | `BIGINT` | `UNSIGNED` → `LARGEINT` |
+| `YEAR` | `SMALLINT` | Read as an integer year; zero year (`0000`) is
preserved as `0`. |
+| `FLOAT` | `FLOAT` | |
+| `DOUBLE` | `DOUBLE` | |
+| `DECIMAL(p,s)` | `DECIMAL(p,s)` | Very high precision falls back to
`STRING`. |
+| `DATE` | `DATE` | |
+| `DATETIME` | `DATETIME(s)` | Preserves microsecond scale from 0 to 6. |
+| `TIMESTAMP` | `DATETIME(s)` | Normalized to the server time zone. |
+| `TIME` | `STRING` | Stored as a string, for example, `12:34:56.000000`. |
+| `CHAR` | `CHAR` | |
+| `VARCHAR` | `VARCHAR` | |
+| `TINYTEXT` / `TEXT` / `MEDIUMTEXT` / `LONGTEXT` | `STRING` | |
+| `BINARY` / `VARBINARY` / `TINYBLOB` / `BLOB` / `MEDIUMBLOB` / `LONGBLOB` |
`STRING` | Base64-encoded string. |
+| `BIT(1)` | `BOOLEAN` | |
+| `BIT(n>1)` | `STRING` | Base64-encoded string. |
+| `JSON` | `STRING` | Stored as JSON text. |
+| `ENUM` | `STRING` | Resolved to the label value. |
+| `SET` | `STRING` | Resolved to comma-separated labels. |
+| Spatial types (`GEOMETRY`, `POINT`, and others) and other types | Not
supported | Automatic table creation fails for a table containing such a
column. Exclude a non-key column with `table.<table_name>.exclude_columns`. |
+
+## Considerations
+
+- Type mapping is based on metadata returned by OceanBase through MySQL
Connector/J.
+- Unsupported types do not fall back to an arbitrary Doris type. Verify the
target table schema before creating a production job.
+- `TIMESTAMP` is affected by the source time zone and the `serverTimezone`
JDBC URL parameter. Set and verify the time zone explicitly for cross-time-zone
deployments.
+- Primary key columns cannot be excluded through
`table.<table_name>.exclude_columns`.
+
+## Related Documents
+
+- [OceanBase CDC with Auto Table
Creation](./continuous-load-oceanbase-database.md)
+- [OceanBase Schema Change Sync](./schema-change-oceanbase.md)
+- [Continuous Load Overview](./continuous-load-overview.md)
diff --git
a/versioned_docs/version-4.x/data-operate/import/import-way/streaming-job/schema-change-mysql.md
b/versioned_docs/version-4.x/data-operate/import/import-way/streaming-job/schema-change-mysql.md
index d4785d657f7..ae10801b3f5 100644
---
a/versioned_docs/version-4.x/data-operate/import/import-way/streaming-job/schema-change-mysql.md
+++
b/versioned_docs/version-4.x/data-operate/import/import-way/streaming-job/schema-change-mysql.md
@@ -40,7 +40,7 @@ MySQL Schema Change Sync is supported from Doris 4.1.4.
- Column positions specified by `FIRST` and `AFTER` are not synchronized to
Doris. New columns are appended after the existing Doris columns.
- `CHANGE COLUMN`, `MODIFY COLUMN`, `RENAME COLUMN`, DEFAULT changes, and
`NULL` / `NOT NULL` constraint changes are not synchronized automatically.
Before performing these operations, pause the continuous load job, change the
Doris target table manually, verify that both schemas are compatible, and then
resume the job.
- Primary key, index, partition, table name, and other table-level schema
changes are not synchronized automatically.
-- You can disable automatic schema change synchronization with the Job
property `schema_change_enabled` (default `true`, supported since version
4.1.4). The `cdc_stream()` table function (SQL Mapping Sync) always forces this
property to `false`.
+- Auto Table Creation Sync enables Schema Change Sync by default. Doris 4.1
does not provide a SQL property to disable it. The `cdc_stream()` table
function (SQL Mapping Sync) disables Schema Change Sync internally.
## Related Docs
diff --git
a/versioned_docs/version-4.x/data-operate/import/import-way/streaming-job/schema-change-oceanbase.md
b/versioned_docs/version-4.x/data-operate/import/import-way/streaming-job/schema-change-oceanbase.md
new file mode 100644
index 00000000000..958b3be3531
--- /dev/null
+++
b/versioned_docs/version-4.x/data-operate/import/import-way/streaming-job/schema-change-oceanbase.md
@@ -0,0 +1,76 @@
+---
+{
+ "title": "OceanBase Schema Change Sync",
+ "language": "en",
+ "sidebar_label": "Schema Change Sync",
+ "description": "Learn which OceanBase schema changes are supported by CDC
Auto Table Creation Sync, how Doris applies them, and their limitations.",
+ "keywords": [
+ "OceanBase Schema Change",
+ "OceanBase CDC",
+ "Auto Table Creation Sync",
+ "continuous load",
+ "ADD COLUMN",
+ "DROP COLUMN"
+ ]
+}
+---
+
+<!-- Knowledge type: Concept -->
+<!-- Applicable scenario: Upstream schema changes during OceanBase Auto Table
Creation Sync -->
+
+OceanBase Schema Change Sync automatically applies upstream column changes to
Doris target tables during continuous load. This capability applies only to
[OceanBase CDC with Auto Table
Creation](./continuous-load-oceanbase-database.md).
+
+:::caution Experimental feature
+
+OceanBase Schema Change Sync is available as an experimental feature starting
from Doris 4.1.4 and supports only MySQL compatibility mode.
+
+:::
+
+OceanBase uses the MySQL CDC schema change processing path, so its supported
changes and behavior are the same as for MySQL.
+
+## Supported Schema Changes
+
+| OceanBase operation | Doris behavior |
+| --- | --- |
+| `ADD COLUMN` | Adds a column with the same name and a type defined by
[OceanBase Data Type Mapping](./data-type-mapping-oceanbase.md), and copies the
column comment. DEFAULT and `NOT NULL` constraints are not copied, and
historical rows are not backfilled. Subsequent rows use the actual values
written by OceanBase to the binlog. |
+| `DROP COLUMN` | Drops the column with the same name. |
+
+## Considerations
+
+- If an added column already exists or a dropped column does not exist, Doris
skips the operation so that retries do not fail the job.
+- Column positions specified by `FIRST` and `AFTER` are not synchronized to
Doris. New columns are appended after existing Doris columns.
+- `CHANGE COLUMN`, `MODIFY COLUMN`, `RENAME COLUMN`, DEFAULT changes, and
`NULL` / `NOT NULL` constraint changes are not synchronized automatically.
+- Primary key, index, partition, table name, and other table-level schema
changes are not synchronized automatically.
+- Before an unsupported schema change, pause the continuous load job, change
the Doris target table manually, verify that both schemas are compatible, and
then resume the job.
+- Auto Table Creation Sync enables Schema Change Sync by default. Doris
currently does not provide a SQL property to disable it.
+
+## Example
+
+Add a column to an OceanBase source table:
+
+```sql
+ALTER TABLE source_db.users ADD COLUMN city VARCHAR(50);
+INSERT INTO source_db.users VALUES (2, 'Alice', 'Hangzhou');
+```
+
+After the job processes the incremental data, the `city` column appears in the
Doris target table:
+
+```sql
+DESC target_db.users;
+```
+
+```text
++-------+--------------+------+-------+---------+-------+
+| Field | Type | Null | Key | Default | Extra |
++-------+--------------+------+-------+---------+-------+
+| id | int | No | true | NULL | |
+| name | varchar(100) | Yes | false | NULL | NONE |
+| city | varchar(50) | Yes | false | NULL | NONE |
++-------+--------------+------+-------+---------+-------+
+```
+
+## Related Documents
+
+- [OceanBase CDC with Auto Table
Creation](./continuous-load-oceanbase-database.md)
+- [OceanBase Data Type Mapping](./data-type-mapping-oceanbase.md)
+- [Continuous Load Overview](./continuous-load-overview.md)
diff --git
a/versioned_docs/version-4.x/data-operate/import/import-way/streaming-job/schema-change-postgresql.md
b/versioned_docs/version-4.x/data-operate/import/import-way/streaming-job/schema-change-postgresql.md
index 4fd65efd667..68686bdaed0 100644
---
a/versioned_docs/version-4.x/data-operate/import/import-way/streaming-job/schema-change-postgresql.md
+++
b/versioned_docs/version-4.x/data-operate/import/import-way/streaming-job/schema-change-postgresql.md
@@ -41,7 +41,7 @@ PostgreSQL Schema Change Sync is supported from Doris 4.1.0.
- If an added column already exists or a dropped column does not exist, Doris
skips the operation so that a retry does not fail the job.
- If one schema change adds and drops columns at the same time, Doris treats
it as a possible column rename and does not automatically change the target
table. This prevents accidental data loss.
- Column renames, column type changes, DEFAULT changes, and `NULL` / `NOT
NULL` constraint changes are not synchronized automatically. Pause the
continuous load job, change the Doris target table manually, verify that both
schemas are compatible, and then resume the job.
-- You can disable automatic schema change synchronization with the Job
property `schema_change_enabled` (default `true`, supported since version
4.1.4). The `cdc_stream()` table function (SQL Mapping Sync) always forces this
property to `false`.
+- Auto Table Creation Sync enables Schema Change Sync by default. Doris 4.1
does not provide a SQL property to disable it. The `cdc_stream()` table
function (SQL Mapping Sync) disables Schema Change Sync internally.
:::caution Behavior change (4.1.4)
diff --git a/versioned_sidebars/version-4.x-sidebars.json
b/versioned_sidebars/version-4.x-sidebars.json
index 94cf78d6fbf..87a47caa8cf 100644
--- a/versioned_sidebars/version-4.x-sidebars.json
+++ b/versioned_sidebars/version-4.x-sidebars.json
@@ -448,6 +448,15 @@
}
]
},
+ {
+ "type": "category",
+ "label": "OceanBase (Experimental)",
+ "items": [
+
"data-operate/import/import-way/streaming-job/continuous-load-oceanbase-database",
+
"data-operate/import/import-way/streaming-job/schema-change-oceanbase",
+
"data-operate/import/import-way/streaming-job/data-type-mapping-oceanbase"
+ ]
+ },
"data-operate/import/import-way/streaming-job/continuous-load-s3"
]
}
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
