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

   Correct the 3.x sequence_type/sequence_col mix-up and distinguish 
ordinary-column values from load-time hidden-column mappings. Clarify full-row 
INSERT requirements, omitted target-column lists, CURRENT_TIMESTAMP defaults 
and partial-update exceptions across active versions.
   
   Fixes #4066
   
   Versions and languages: dev, 4.x and 3.x; English and Chinese.
   
   Source verification:
   - branch-3.0/3.1/4.0 and master BindSink distinguish mapped ordinary columns 
from the unmapped hidden Sequence column; omitted INSERT column lists include 
the mapped column
   - branch-3.1 DataDescription.analyzeSequenceCol returns immediately when a 
table already has a Sequence map column
   - Current/4.x mapping sections already distinguish sequence_type; their 
broad caution had the same ambiguity
   
   Validation:
   - Checked both corrected 3.x mapping paragraphs against load source
   - Reviewed sequence checks and partial-update exceptions in BindSink across 
active branches
   - Confirmed six locale/version copies express equivalent requirements
   - git diff --check
   
   Review:
   - Goal: correct the reported documentation issue; the changed content 
directly addresses it.
   - Scope: targeted documentation edits.
   - Information architecture: active version and locale counterparts 
inspected; archived snapshots unchanged.
   - Navigation: no paths, slugs, anchors or sidebar entries changed.
   - Frontend/build: no framework, styling or build-script changes.
   - Validation limits: no live Doris execution or full website build performed.
   - Other concerns: No additional correctness, usability, accessibility, SEO 
or maintainability issues found in the changed content.
   


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