boluor opened a new pull request, #3842:
URL: https://github.com/apache/doris-website/pull/3842
## Summary
Three pages whose examples reference an object the page itself never
creates. On a fresh cluster the very first example fails — they only ever
worked by accident when an earlier page in the sweep had left the object
behind. Same shape as the earlier Bucket-1 / `ALTER-USER.md` (#3840)
missing-setup work; newly exposed once the verifier started cleaning up
cluster-global namespaces (users / roles / SQL block rules / top-level
databases) between pages.
| Page | Missing setup added |
|------|---------------------|
| `DROP-DATABASE.md` | `CREATE DATABASE db_test;` |
| `DROP-ROLE.md` | `CREATE ROLE role1;` |
| `data-bucketing.md` | `CREATE DATABASE IF NOT EXISTS demo;` (the examples
qualify `hash_bucket_tbl` / `random_bucket_tbl` / `dynamic_partition_tbl` with
`demo.`) |
Mirrored each change in EN and ZH. Verified end-to-end on Doris 4.1.1.
## Scope note
`REVOKE-FROM.md` regressed on the same triage but is not in this PR — its
examples reference six different cluster-scoped objects (`jack@'192.%'`,
`role1`/`role2`/`my_role`/`test_role`, workload group `g1`, …) plus one
statement (`REVOKE 'role1','role2' FROM ROLE 'test_role'`) whose syntax 4.1.1's
parser rejects. Properly fixing that page is a larger piece of work and is
deferred.
## Verification
```sql
-- DROP-DATABASE.md flow
CREATE DATABASE db_test;
DROP DATABASE db_test;
-- DROP-ROLE.md flow
CREATE ROLE role1;
DROP ROLE role1;
-- data-bucketing.md flow
CREATE DATABASE IF NOT EXISTS demo;
CREATE TABLE demo.hash_bucket_tbl(oid BIGINT, dt DATE, region VARCHAR(10),
amount INT)
DUPLICATE KEY(oid) DISTRIBUTED BY HASH(oid) BUCKETS 1
PROPERTIES("replication_num"="1");
DROP TABLE demo.hash_bucket_tbl;
```
All succeed on Doris 4.1.1.
🤖 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]
