Skip to content

Conversation

@tianchen92
Copy link
Contributor

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

  • log the creation of the web directory on INFO instead of the warning

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:

  • Dependencies (does it add or upgrade a dependency): (no)
  • The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
  • The serializers: (no)
  • The runtime per-record code paths (performance sensitive): (no)
  • Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
  • The S3 file system connector: (no)

Documentation

  • Does this pull request introduce a new feature? (no)
  • If yes, how is the feature documented? (not applicable)

@flinkbot
Copy link
Collaborator

flinkbot commented Apr 19, 2019

Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community
to review your pull request. We will use this comment to track the progress of the review.

Review Progress

  • ✅ 1. The [description] looks good.
  • ✅ 2. There is [consensus] that the contribution should go into to Flink.
  • ❓ 3. Needs [attention] from.
  • ✅ 4. The change fits into the overall [architecture].
  • ❓ 5. Overall code [quality] is good.

Please see the Pull Request Review Guide for a full explanation of the review process.

Details
The 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 commands
The @flinkbot bot supports the following commands:

  • @flinkbot approve description to approve one or more aspects (aspects: description, consensus, architecture and quality)
  • @flinkbot approve all to approve all aspects
  • @flinkbot approve-until architecture to approve everything until architecture
  • @flinkbot attention @username1 [@username2 ..] to require somebody's attention
  • @flinkbot disapprove architecture to remove an approval you gave earlier

@tianchen92
Copy link
Contributor Author

Hi @uce, could you please help review this PR? thanks

@zentol
Copy link
Contributor

zentol commented Apr 24, 2019

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.

@zentol zentol self-assigned this Apr 24, 2019
@uce
Copy link
Contributor

uce commented Apr 24, 2019

I agree with @zentol.

@tianchen92
Copy link
Contributor Author

@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?
I am just not sure how to confirm which is initial startup. Is createUploadDir invoked in RestServerEndpoint constructor the initial startup and others in FileUploadHandler not?
Thanks!

@zentol
Copy link
Contributor

zentol commented Apr 25, 2019

add a param in createUploadDir to identify whether it‘s the initial startup

yes.

createUploadDir invoked in RestServerEndpoint constructor [is] the initial startup and others in FileUploadHandler not

yes

@zentol
Copy link
Contributor

zentol commented Apr 25, 2019

@flinkbot approve-until architecture

@tianchen92
Copy link
Contributor Author

Thanks for your reply @zentol, I have resolved the comments, please have a look.

@zentol zentol merged commit 74dc909 into apache:master Apr 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants