boluor opened a new pull request, #3850: URL: https://github.com/apache/doris-website/pull/3850
## Summary The Examples section ran a dozen `REVOKE` statements against users, roles, workload group `g1`, compute group `group1`, storage vault `vault1`, etc. **without ever showing a single CREATE / GRANT**. On a fresh cluster every example fails — same shape as the earlier Bucket-1 / ALTER-USER / DROP-DATABASE / DROP-ROLE / data-bucketing missing-setup family. ## Changes **Added** at the top of the Examples section: a single Setup block that 1. creates the users (`jack@'192.%'`, `jack@'%'`), roles (`role1`, `role2`, `my_role`, plus `test_role` on the ZH side), the `db1` database, and workload group `g1`; 2. runs the prerequisite `GRANT` statements so each subsequent `REVOKE` has something to remove (you can't revoke a privilege that was never granted). **Removed** (EN only): the example ```sql REVOKE 'role1','role2' FROM ROLE 'test_role'; ``` The page's own Syntax block (line 43) only documents: ``` REVOKE <role_list> FROM <user_identity> ``` That syntax does **not** allow `FROM ROLE <name>` for the role-list form, and 4.1.1's parser rejects the statement as `extraneous input 'ROLE'`. The example contradicted the page's spec and didn't work on the documented version. The ZH page also has an example with `FROM ROLE` at the same position, but it's a **different** statement (`REVOKE USAGE_PRIV ON WORKLOAD GROUP 'g1' FROM ROLE 'test_role'`) — that one **is** supported and is kept. ## Verification End-to-end on a fresh Doris 4.1.1 cluster: ``` Setup block: OK All 10 EN REVOKE examples: OK All 11 ZH REVOKE examples: OK ``` ## Related 4.x missing-setup PRs (now closed) #3821-#3827 (Bucket 1) · #3840 (ALTER-USER) · #3842 (DROP-DATABASE / DROP-ROLE / data-bucketing) · **#this** (REVOKE-FROM). Same set has been backported to dev/master in #3846. 🤖 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]
