fix(data-security): exist sensitive is not filtered and view desensitization data failed #509
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
type-bug
module-data security
What this PR does / why we need it:
There are two bug:
This PR fix above two bugs. Table name and column name stored in ODC metaDB is case-insensitive. So ODC cannot deal with sensitive columns with same name in different case. So, ODC will defaultly change the object name to lowcase in MySQL mode and uppercase in Oracle mode. If the object name is quoted, then ODC will keep the case themselves.
Which issue(s) this PR fixes:
Fixes #475
Special notes for your reviewer:
Self-test passed