JNSimba opened a new pull request, #3933:
URL: https://github.com/apache/doris-website/pull/3933

   ## Summary
   
   Fix incorrect Streaming Job (CDC continuous load) syntax in the docs and add 
a dedicated data type mapping reference page. Applied to both **dev (current)** 
and **version-4.x**, EN + ZH.
   
   ## Syntax fixes (verified against the SQL parser grammar and regression 
cases)
   
   - **`PROPERTIES` placement**: must come **before** `ON STREAMING` (right 
after the job name), not after. The previous order would fail to parse.
   - **`max_interval`**: an integer number of **seconds** (e.g. `10`); a unit 
suffix like `10s` is not accepted.
   - **`s3.max_batch_bytes`**: a plain **byte count** (e.g. `10737418240`, 
valid range 100MB–10GB); `10G` is not accepted.
   - **`offset`**:
     - Multi-table CDC (`FROM ... TO DATABASE`) defaults to `latest` (was 
documented as `initial`).
     - `cdc_stream` TVF requires `offset` (it has no default); fixed the param 
tables and the examples that omitted it (and a trailing-comma issue in the zh 
examples).
   
   ## Docs improvements
   
   - **Continuous Load Overview**: add a **Limitations** section (primary-key 
tables only; schema-change/DDL sync scope) placed just above the FAQ, and link 
to the new mapping page.
   - **New page – Data Type Mapping**: how upstream MySQL/PostgreSQL column 
types map to Doris column types, with value-representation notes (unsigned 
widening, JSON, Base64-encoded binary, timezone normalization, GeoJSON, 
one-dimensional arrays, etc.). Registered in the sidebars.
   
   No behavior change — documentation only.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to