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

   Document S3 notification and one-time ingestion alongside ordered ingestion, 
with separate task guides under a compact S3 sidebar. Cover setup, examples, 
mode selection, delivery semantics, monitoring, and recovery while preserving 
the existing S3 overview URL.
   
   Update the Chinese dev and 4.x CDC guides and Job SQL references for 
`schema_change_behavior`, supported schema changes, and manual recovery. 
English S3 source pages are synchronized because they also register the 
localized routes. English CDC and Job-reference updates are deferred; this PR 
intentionally follows the requested Chinese-first scope. Other historical 
versions are unchanged.
   
   Validation: compiled all 38 changed Markdown files, parsed 8 JSON examples, 
checked English/Chinese S3 example consistency, and loaded both locales' 
dev/4.x routes and sidebars. The documentation governance report and `git diff 
--check` report no errors. A separate content review found no blocking issues. 
Full production builds and live AWS/Doris examples were not run.
   
   ## Versions
   
   - [x] dev
   - [x] 4.x
   - [ ] 3.x
   - [ ] 2.1 or older (not covered by version/language sync gate)
   
   ## Languages
   
   - [x] Chinese
   - [x] English (S3 guides)
   
   ## 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
   


-- 
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