[opt](audit) use one line in audit log and origin statement in audit table#52032
Merged
morningman merged 4 commits intoapache:masterfrom Jun 20, 2025
Merged
[opt](audit) use one line in audit log and origin statement in audit table#52032morningman merged 4 commits intoapache:masterfrom
morningman merged 4 commits intoapache:masterfrom
Conversation
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
98b06c5 to
6735857
Compare
06fd181 to
72fdf8d
Compare
Contributor
Author
|
run buildall |
TPC-H: Total hot run time: 34577 ms |
TPC-DS: Total hot run time: 185993 ms |
ClickBench: Total hot run time: 29.25 s |
Contributor
FE UT Coverage ReportIncrement line coverage |
Contributor
Author
|
run buildall |
morrySnow
approved these changes
Jun 20, 2025
Contributor
|
PR approved by at least one committer and no changes requested. |
Contributor
|
PR approved by anyone and no changes requested. |
TPC-H: Total hot run time: 34266 ms |
TPC-DS: Total hot run time: 186068 ms |
ClickBench: Total hot run time: 29.29 s |
Contributor
FE UT Coverage ReportIncrement line coverage |
CalvinKirs
approved these changes
Jun 20, 2025
morningman
added a commit
to morningman/doris
that referenced
this pull request
Jun 24, 2025
…table (apache#52032) Previously, when auditing, we use replace all `\n`, `\t` in origin sql string with `\\n`, `\\t`, so that the sql string can be written in one line. But this lead to some problem: 1. User can not direct use the sql in audit log to execute. 2. Some replacement is wrong, eg, replace the `\n` in a quota string. This PR changes the logic: 1. For audit log, only replace `\n` with `\\n` to keep SQL in one line. 2. For audit table, keep the origin string. 3. Use special column and line separator for audit log load data, to avoid conflict with char in SQL
morningman
added a commit
that referenced
this pull request
Jun 24, 2025
16 tasks
hello-stephen
pushed a commit
that referenced
this pull request
Jul 7, 2025
### What problem does this PR solve? Related PR: In this PR #52032 , the audit_log schema had changed, so the test need to fix
morningman
added a commit
that referenced
this pull request
Jul 9, 2025
followup #52032, the separator is wrong
morningman
added a commit
to morningman/doris
that referenced
this pull request
Jul 9, 2025
…table (apache#52032) Previously, when auditing, we use replace all `\n`, `\t` in origin sql string with `\\n`, `\\t`, so that the sql string can be written in one line. But this lead to some problem: 1. User can not direct use the sql in audit log to execute. 2. Some replacement is wrong, eg, replace the `\n` in a quota string. This PR changes the logic: 1. For audit log, only replace `\n` with `\\n` to keep SQL in one line. 2. For audit table, keep the origin string. 3. Use special column and line separator for audit log load data, to avoid conflict with char in SQL
morningman
pushed a commit
to morningman/doris
that referenced
this pull request
Jul 9, 2025
### What problem does this PR solve? Related PR: In this PR apache#52032 , the audit_log schema had changed, so the test need to fix
morningman
added a commit
to morningman/doris
that referenced
this pull request
Jul 9, 2025
…52968) followup apache#52032, the separator is wrong
morrySnow
pushed a commit
that referenced
this pull request
Jul 10, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 problem does this PR solve?
Previously, when auditing, we use replace all
\n,\tin origin sql string with\\n,\\t,so that the sql string can be written in one line. But this lead to some problem:
\nin a quota string.This PR changes the logic:
\nwith\\nto keep SQL in one line.Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)