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

   ## Versions
   
   - [x] dev
   - [ ] 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
   - [x] 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
   
   ## Summary
   
   Related implementation: https://github.com/apache/doris/pull/68791
   
   Document `external_scan_consistent_hash_spread_num` in the existing English 
and Chinese session-variable reference:
   
   - Default `1` preserves original scheduling; it does not mean a single 
backend.
   - Explicit `0` enables automatic spreading across eligible compute-group 
backends.
   - Values above `1` bound hash candidates when file caching or consistent 
hashing is enabled.
   - Explain query-local weights, random ties, single assignment, locality, 
global redistribution, cache costs, and persisted global values.
   
   Only the current development documentation is updated because this feature 
is proposed for master and has not been released or backported. Existing page 
paths, front matter, sidebar entries and released-version documentation are 
unchanged.
   
   ## Validation
   
   - The repository's `scripts/check_md_links_single.py --no-external` passes 
for both changed pages.
   - Front matter, heading hierarchy, fenced SQL blocks, existing sidebar 
placement and English/Chinese semantic consistency were checked.
   - Implementation validation: 33 focused FE unit tests, standard FE 
build/Checkstyle, and the session-variable and external-scan regression suites 
passed. These cover the default, opt-in modes, bounds and reset behavior.
   - A full Docusaurus site build was not run locally; the repository build 
workflow remains required.
   


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