-
Notifications
You must be signed in to change notification settings - Fork 9.2k
HADOOP-18014. CallerContext should not include some characters. #3683
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
Conversation
|
💔 -1 overall
This message was automatically generated. |
virajjasani
left a comment
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.
Left a minor nit, +1 (non-binding) otherwise
| for (String str: ILLEGAL_CHARACTERS) { | ||
| if (context.contains(str)) { | ||
| return false; | ||
| } | ||
| } | ||
|
|
||
| return true; |
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.
nit: could be replaced with return ILLEGAL_CHARACTERS.stream().noneMatch(context::contains).
|
@ferhui @goiri @virajjasani Thank you for your reviews. |
Description of PR
CallerContext should not include '\t', '\n', '=' because it could be written to audit log.
How was this patch tested?
I created a unit test and confirmed that it succeeded.
For code changes: