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

   ## Summary
   
   Doc page (4.x): \`sql-statements/table-and-view/table/SHOW-PARTITION.md\` 
(EN).
   
   The example uses a hard-coded partition ID \`13004\` and shows a 1-row 
sample output as if it were the literal expected result. On any fresh cluster 
(e.g. our Apache Doris 4.1.1 verification rig) that partition does not exist, 
so the actual output is an empty result set. The doc was internally 
over-promising. ZH already fenced the same result as \`\`\`\`sql\`\`\`\`, which 
renders the same and signals \"look-like\" rather than \"literal expected\".
   
   Two adjustments to EN:
   - Replace the bare \"Results:\" lead-in with a one-paragraph note that calls 
out \`13004\` is illustrative (point at \`SHOW PARTITIONS\`) and that the 
function returns an empty set if no partition matches.
   - Align the fence to \`\`\`\`sql\`\`\`\` matching ZH, so the verifier 
doesn't try to strict-compare the illustrative row.
   
   ## Verification
   
   On a single-node Apache Doris 4.1.1 cluster:
   
   \`\`\`
   mysql> SHOW PARTITION 13004;
   Empty set (0.01 sec)
   \`\`\`
   
   A longer-term fix would be to add a setup block that creates a table, calls 
\`SHOW PARTITIONS\` to capture a real partition ID, and then uses that ID in 
\`SHOW PARTITION\`. That is a much bigger restructure; this PR is the minimum 
honest fix.
   
   ## Test plan
   
   - [x] Run \`SHOW PARTITION 13004\` on a 4.1.1 cluster — 0 rows.
   - [x] Prose accurately describes the actual behavior for both \"partition 
exists\" and \"does not exist\" cases.
   - [x] No content lost; sample output table preserved unchanged.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


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