-
Notifications
You must be signed in to change notification settings - Fork 13.3k
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
[FLINK-12491][docs][configuration] Fix incorrect javadoc for path sep… #8418
base: master
Are you sure you want to change the base?
Conversation
Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community Automated ChecksLast check on commit 8a6f4f9 (Fri May 28 06:59:36 UTC 2021) Warnings:
Mention the bot in a comment to re-run the automated checks. Review Progress
Please see the Pull Request Review Guide for a full explanation of the review process. 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 commandsThe @flinkbot bot supports the following commands:
|
e1f747d
to
15fc612
Compare
Hi @kezhuw, |
@flinkbot approve description |
@dawidwys After dug deeper, I found the history of used path separators:
I look at ˋflink-conf.yamlˋ in master (518616e https://github.com/apache/flink/blob/master/flink-dist/src/main/resources/flink-conf.yaml#L153), it says that:
So I think it is a mistake in documentation not code. Besides the history, I think it is distractive to support more separators. What do you think ? |
What do you think @aljoscha? Which separators should we support? |
@dawidwys @aljoscha I think current the two path separators serve their "purposes" if there is any:
A new os-agnostic path separator introduces nothing but distraction in my opinion. |
Isn't the problem that someone interpreted the |
@aljoscha I think this is the case when that javadoc was introduced in commit a7c407a#diff-125ce56ea60a577549026859d5d9a4e0 . |
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.
Hi,
I think then we can remove the |
from the docs. I will try to review the PR in the coming days. So far I found one place that needs an update.
@@ -210,7 +210,7 @@ | |||
|
|||
/** | |||
* The config parameter defining the directories for temporary files, separated by | |||
* ",", "|", or the system's {@link java.io.File#pathSeparator}. | |||
* "," or the system's {@link java.io.File#pathSeparator}. |
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.
Update also the description in TMP_DIRS.withDescription
few lines below.
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.
Have fixed.
cafdb91
to
df6d3f5
Compare
@dawidwys Could you take time to review this pull request ? It has been more that one month past since your last review comment. |
df6d3f5
to
fe55dec
Compare
@flinkbot run azure |
…arators of CoreOptions.TMP_DIRS
fe55dec
to
8a6f4f9
Compare
@flinkbot run azure |
1 similar comment
@flinkbot run azure |
…arators of CoreOptions.TMP_DIRS
What is the purpose of the change
Fix incorrect javadoc for path separators part of
CoreOptions.TMP_DIRS
andConfigConstants.TASK_MANAGER_TMP_DIR_KEY
Brief change log
CoreOptions.TMP_DIRS
andConfigConstants.TASK_MANAGER_TMP_DIR_KEY
.ConfigurationUtils.splitPaths
so we can test both unix and windows path separators without demand on ci test matrix.Verifying this change
This change added tests and can be verified as follows:
Does this pull request potentially affect one of the following parts:
@Public(Evolving)
: (no)Documentation