-
Notifications
You must be signed in to change notification settings - Fork 13.9k
[FLINK-10441]Don't log warning when creating upload directory #8219
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
|
Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community Review Progress
Please see the Pull Request Review Guide for a full explanation of the review process. DetailsThe Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commandsThe @flinkbot bot supports the following commands:
|
|
Hi @uce, could you please help review this PR? thanks |
|
This is not the correct fix imo. So, the message is logged as WARN on purpose since we've had cases in the past where this directory was removed without a user realizing it. The correct fix would be to log it on INFO only on the initial startup (at which point we expect the directory to not exist), but on WARN after that. |
|
I agree with @zentol. |
|
@zentol @uce Thanks for your detailed comments, I have got your point. Is it right to add a param in createUploadDir to identify whether it‘s the initial startup, then we can decide log it on INFO level or Warning level? |
yes.
yes |
|
@flinkbot approve-until architecture |
|
Thanks for your reply @zentol, I have resolved the comments, please have a look. |
What is the purpose of the change
This PR is related to FLINK-10441. RestServerEndpoint.createUploadDir(Path, Logger) logs a warning if the upload directory does not exist, it's better to log the creation of the web directory on INFO instead of the warning.
Brief change log
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
@Public(Evolving): (no)Documentation