Gabriel39 opened a new pull request, #4675: URL: https://github.com/apache/doris-website/pull/4675
## What changes Catalog documentation currently shows a password mask without explaining which other credentials are protected or how URI values are handled. Add a bilingual development-version reference for the masking policy introduced by apache/doris#70705, with links from the Catalog overview, SHOW references and FE configuration. The reference explains: - Supported SHOW, audit, lineage and typed-diagnostic output paths; masking markers, omitted properties and the distinction from metadata encryption. - The union of built-in/registered secret names, connector namespaces, permanent SDK/Hadoop/JDBC rules and the configurable supplemental name regex. - Representative credentials for Catalog/metastore and storage providers, including MaxCompute session tokens, Ozone access keys, native SDK credentials and Hadoop custom properties. - Whole-value JDBC masking; visible plain hosts; URL userinfo/fragment removal and query-value masking; whole-value masking of signatures, ambiguous formats and invalid addresses. - Native storage/path exceptions and the separate internal streaming-S3 audit behavior. - `datasource_sensitive_property_pattern`: default, replacement semantics, disabling only supplemental matches, empty/invalid expressions, FE-local consistency and persistence. - Limits for URL paths, unrecognized query parameters, arbitrary SDK containers, comments and free text, with synthetic examples and operational guidance. Update dev SHOW examples to hide `jdbc_url`, mark terminal output as text and distinguish real masking markers from placeholders. Repair two existing heading links in the touched Chinese 3.x Catalog overview. ## Version and language scope The full reference, sidebar entry and new FE parameter documentation are intentionally dev-only. The active 4.x/3.x Catalog overview and SHOW pages receive matching English/Chinese scope notices explaining that a masked password does not establish complete credential coverage. Do not copy the new policy into every released version: the related 4.2 backport is tracked by apache/doris#70776, and neither that PR nor a broad version-family label establishes support in every released build. No release patch number is invented. The governance warning about the missing 4.x full-reference counterpart is intentional for this reason. Both English and Chinese are updated for every affected version/topic. ## Validation - Reviewed the complete staged diff against the merged implementation, corrected review findings and repeated the local self-review using all seven website review checkpoints. - Native Docusaurus EN/zh-CN sample build across dev, 4.x and 3.x, including every changed document; static verification and focused browser checks for the new reference, navigation, localized content, version notices, JDBC masking examples and configuration anchors. - Internal-link/anchor checks for all 22 changed Markdown files; identical code blocks and inline property names between the new English and Chinese references. - Changed-file documentation governance: zero errors. Existing warnings and the intentional dev-only version asymmetry are documented. - Staged Gitleaks scan, submitted-content privacy/scope checks and whitespace validation. Validation is a bounded bilingual sample, not a full five-locale publication build. Browser checks serve the sample's own CDN assets locally, following the existing preview verification approach. No external Catalog credentials or live connector setup are required or used. No runtime code or new product test cases are included. ## Versions - [x] dev - [x] 4.x - [x] 3.x - [ ] 2.1 or older (not covered by version/language sync gate) ## Languages - [x] Chinese - [x] English ## Docs Checklist - [x] Checked by AI - [ ] Test Cases Built (documentation-only; existing native build/link/browser checks are used) - [x] Updated required version and language counterparts, or explained why not - [x] If only one language changed, confirmed whether source/translation counterparts need sync (both updated) -- 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]
