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

   ## Summary
   
   The Examples section on both EN and ZH runs four `ALTER USER` statements 
against `jack@'%'` without ever showing the `CREATE USER` statement that puts 
`jack` in place. Anyone copy-pasting from the doc into a fresh cluster hits 
`User 'jack'@'%' does not exist` on the very first example.
   
   Added a setup block at the top of the Examples section that creates `jack` 
first. This mirrors the pattern used by other Account Management pages and by 
the recently merged Bucket-1 missing-setup fixes.
   
   ## Verification
   
   End-to-end on a fresh Doris 4.1.1 cluster:
   
   ```sql
   CREATE USER jack@'%' IDENTIFIED BY "12345";
   ALTER USER jack@'%' IDENTIFIED BY "abcde";
   ALTER USER jack@'%' FAILED_LOGIN_ATTEMPTS 3 PASSWORD_LOCK_TIME 1 DAY;
   ALTER USER jack@'%' ACCOUNT_UNLOCK;
   ALTER USER jack@'%' COMMENT "this is my first user";
   -- all five statements succeed
   ```
   
   ## Related
   
   Surfaced by the doc verifier re-sweep on 2026-05-29 against a freshly 
redeployed cluster. The other three "P0" pages on that triage 
(`sql-blocking.md`, `PLAN-REPLAYER-DUMP.md`, `CREATE-ROLE.md`) are not in this 
PR — they work cleanly on a fresh cluster on first run, and their re-run 
failures are tool-harness pollution against shared global namespaces 
(SQL_BLOCK_RULE, top-level DATABASE, ROLE) rather than doc bugs. That class of 
issue is already recorded in `doris-verify/ISSUES.md` for tool follow-up.
   
   🤖 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