Skip to content
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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

kezhuw
Copy link
Member

@kezhuw kezhuw commented May 11, 2019

…arators of CoreOptions.TMP_DIRS

What is the purpose of the change

Fix incorrect javadoc for path separators part of CoreOptions.TMP_DIRS and ConfigConstants.TASK_MANAGER_TMP_DIR_KEY

Brief change log

  • Fix incorrect javadoc for path separators part of CoreOptions.TMP_DIRS and ConfigConstants.TASK_MANAGER_TMP_DIR_KEY.
  • Refactor 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:

  • Added test for documented path separators.

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 May 11, 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.

Automated Checks

Last check on commit 8a6f4f9 (Fri May 28 06:59:36 UTC 2021)

Warnings:

  • No documentation files were touched! Remember to keep the Flink docs up to date!

Mention the bot in a comment to re-run the automated checks.

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.


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

@dawidwys
Copy link
Contributor

Hi @kezhuw,
Thank you for your contribution. I think your correct that there is a problem in org.apache.flink.configuration.ConfigurationUtils#splitPaths, but rather than adjusting the javadocs (and docs) to the broken code, how about we fix the method?

@dawidwys
Copy link
Contributor

@flinkbot approve description

@kezhuw
Copy link
Member Author

kezhuw commented May 13, 2019

@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:

Add a delimited list for multiple directories, using the system directory delimiter (colon ':' on unix) or a comma, e.g.: /data1/tmp:/data2/tmp:/data3/tmp

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 ?

@dawidwys
Copy link
Contributor

What do you think @aljoscha? Which separators should we support?

@kezhuw
Copy link
Member Author

kezhuw commented May 14, 2019

@dawidwys @aljoscha I think current the two path separators serve their "purposes" if there is any:

  • ˋFile.pathSeparatorˋ is same as os's path separator, it fits target os's convention.
  • ˋ,ˋ provides os-agnostic path separator, so we can configure separated file paths cross os.

A new os-agnostic path separator introduces nothing but distraction in my opinion.

@aljoscha
Copy link
Contributor

Isn't the problem that someone interpreted the | as an actual separator and not as the regex syntax that it is?

@kezhuw
Copy link
Member Author

kezhuw commented May 15, 2019

@aljoscha I think this is the case when that javadoc was introduced in commit a7c407a#diff-125ce56ea60a577549026859d5d9a4e0 .

@kezhuw
Copy link
Member Author

kezhuw commented May 20, 2019

@dawidwys @aljoscha Hi, is there any consensus on this issue ?

Copy link
Contributor

@dawidwys dawidwys left a 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}.
Copy link
Contributor

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.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have fixed.

@kezhuw
Copy link
Member Author

kezhuw commented Jul 9, 2019

@flinkbot attention @dawidwys

@flinkbot
Copy link
Collaborator

flinkbot commented Jul 9, 2019

CI report for commit cafdb91: FAILURE Build

@kezhuw kezhuw force-pushed the fix-path-separator-documentation branch from cafdb91 to df6d3f5 Compare July 10, 2019 14:22
@kezhuw
Copy link
Member Author

kezhuw commented Jul 10, 2019

@dawidwys Could you take time to review this pull request ? It has been more that one month past since your last review comment.

@flinkbot
Copy link
Collaborator

CI report for commit df6d3f5: SUCCESS Build

@flinkbot
Copy link
Collaborator

flinkbot commented Aug 6, 2019

CI report:

@kezhuw kezhuw force-pushed the fix-path-separator-documentation branch from df6d3f5 to fe55dec Compare December 19, 2020 13:59
@kezhuw
Copy link
Member Author

kezhuw commented Dec 19, 2020

@flinkbot run azure

@flinkbot
Copy link
Collaborator

flinkbot commented Dec 19, 2020

CI report:

Bot commands The @flinkbot bot supports the following commands:
  • @flinkbot run azure re-run the last Azure build

@kezhuw
Copy link
Member Author

kezhuw commented Dec 20, 2020

@dawidwys @aljoscha Could you have time to review this pr ? We have forgotten it for a long time.

@kezhuw kezhuw force-pushed the fix-path-separator-documentation branch from fe55dec to 8a6f4f9 Compare January 1, 2021 12:55
@kezhuw
Copy link
Member Author

kezhuw commented Jan 2, 2021

@flinkbot run azure

1 similar comment
@kezhuw
Copy link
Member Author

kezhuw commented Jan 2, 2021

@flinkbot run azure

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