*: add column-level masking policy feature document#21454
Conversation
|
@tiancaiamao Please involve a tech reviewer for this PR. Thanks. |
|
Please address the comments~ |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Co-authored-by: Grace Cai <qqzczy@126.com>
Co-authored-by: Grace Cai <qqzczy@126.com>
|
Test User seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
# Conflicts: # sql-statements/sql-statement-overview.md
Add SQL statement docs for the column-level data masking feature: - New: sql-statement-create-masking-policy.md (CREATE MASKING POLICY) - New: sql-statement-show-masking-policies.md (SHOW MASKING POLICIES) - Updated: sql-statement-alter-table.md (ADD/DROP/ENABLE/DISABLE/MODIFY MASKING POLICY) - Updated: sql-statement-overview.md (add masking entries to DDL and SHOW tables) - Updated: TOC.md (add new statement entries) Refs: #21454
ee1411a to
6f7e786
Compare
|
Add sql-statement related part, PTAL @qiancai |
[LGTM Timeline notifier]Timeline:
|
| - **返回规则** | ||
| - **字符串** → 返回相同长度的字符串,所有字符替换为 `'X'` | ||
| - **日期/DATETIME/TIMESTAMP** → 返回 `1970-01-01`(保留原始类型和小数秒精度) | ||
| - **Duration** → 返回 `00:00:00` |
| - **字符串类型**:`VARCHAR`、`CHAR`、`TEXT` 及其变体 | ||
| - **二进制类型**:`BINARY`、`VARBINARY`、`BLOB` | ||
| - **日期和时间类型**:`DATE`、`TIME`、`DATETIME`、`TIMESTAMP`、`YEAR` | ||
|
|
There was a problem hiding this comment.
不支持数值类型
支持这些:
- VARCHAR, CHAR, TEXT(TINYTEXT, MEDIUMTEXT, LONGTEXT), BLOB(TINYBLOB, MEDIUMBLOB, LONGBLOB)
- For the LONGTEXT and BLOB types, full masking (full redaction) or NULL masking needs to be supported.
- DATE, TIME,DATETIME,TIMESTAMP,YEAR
Co-authored-by: Grace Cai <qqzczy@126.com>
|
PTAL @bb7133 |
|
@expxiaoli: adding LGTM is restricted to approvers and reviewers in OWNERS files. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/retest |
|
@tiancaiamao: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |

First-time contributors' checklist
What is changed, added or deleted? (Required)
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions (in Chinese).
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?