Skip to content

[feat][COM][common] add code privacy protection for engine logging#1000

Open
v-kkhuang wants to merge 1 commit intodev-2.0.0from
dev-2.0.0-disable-code-log
Open

[feat][COM][common] add code privacy protection for engine logging#1000
v-kkhuang wants to merge 1 commit intodev-2.0.0from
dev-2.0.0-disable-code-log

Conversation

@v-kkhuang
Copy link
Copy Markdown

What is the purpose of the change

Background/Problem:
Currently, engine executors log raw code which may contain sensitive information such as passwords, API keys, or other confidential data. This poses a security risk as sensitive information can be exposed in log files, potentially compromising user privacy and system security.

Purpose of Change:
To address this problem, this PR adds code privacy protection by introducing a CodeUtils utility class that filters sensitive information from code before logging. The feature is integrated across multiple engine executors to automatically protect sensitive data.

Value/Impact:
After the change, sensitive code information is automatically filtered from engine logs, improving security and protecting user privacy without affecting engine functionality.

Related issues/PRs

Related issues: close #999
Related pr:none

Brief change log

  • Add CodeUtils utility class for code privacy filtering
  • Update doris engine executor to use CodeUtils for code filtering
  • Update elasticsearch engine executor to use CodeUtils
  • Update flink engine executors to use CodeUtils
  • Update impala engine executor to use CodeUtils
  • Update nebula engine executor to use CodeUtils
  • Update presto engine executor to use CodeUtils
  • Update repl engine executor to use CodeUtils
  • Update spark engine executors to use CodeUtils
  • Update trino engine executor to use CodeUtils

Checklist

  • I have read the Contributing Guidelines on pull requests.
  • I have explained the need for this PR and the problem it solves
  • I have explained the changes or the new features added to this PR
  • I have added tests corresponding to this change
  • I have updated the documentation to reflect this change
  • I have verified that this change is backward compatible
  • If this is a code change: I have written unit tests to fully verify the new behavior.

@v-kkhuang v-kkhuang added the enhancement New feature or request label Apr 23, 2026
Copy link
Copy Markdown

@casionone casionone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants