-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[enhance](auth)The priority of attributes is higher than session variable #47185
Conversation
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
run buildall |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add test cases
TPC-H: Total hot run time: 32245 ms
|
TPC-DS: Total hot run time: 186522 ms
|
ClickBench: Total hot run time: 29.83 s
|
run buildall |
TPC-H: Total hot run time: 32351 ms
|
TPC-DS: Total hot run time: 193499 ms
|
ClickBench: Total hot run time: 30.92 s
|
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
…able (apache#47185) The current priority is that session variable is higher than user property, which is incorrect because session variable can be set freely by ordinary users and will bypass the restrictions set by administrators Scope of Impact: - getInsertTimeoutS - getQueryTimeoutS - getMaxExecMemByte
…able (apache#47185) ### What problem does this PR solve? The current priority is that session variable is higher than user property, which is incorrect because session variable can be set freely by ordinary users and will bypass the restrictions set by administrators Scope of Impact: - getInsertTimeoutS - getQueryTimeoutS - getMaxExecMemByte
What problem does this PR solve?
The current priority is that session variable is higher than user property, which is incorrect because session variable can be set freely by ordinary users and will bypass the restrictions set by administrators
Scope of Impact:
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)