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-14839][config] Let JobGraph#classpaths become non-null #10235

Closed
wants to merge 4 commits into from

Conversation

tisonkun
Copy link
Member

What is the purpose of the change

JobGraph#userJars & JobGraph#classpaths are non-null, so we can improve our codes a bit.

Brief change log

  • Let JobGraph#classpaths become non-null. Preciously, we now add classpaths into an ArrayList instead of changing the reference.
  • Thus, rename setClasspaths to addClasspaths
  • BlobLibraryCacheManager#registerTask never receives nullable parameter, indeed.

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)

cc @zentol @GJL

*
* @return True, if the JobGraph has user code JAR files attached, false otherwise.
*/
public boolean hasUsercodeJarFiles() {
Copy link
Member Author

Choose a reason for hiding this comment

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

unused

@flinkbot
Copy link
Collaborator

flinkbot commented Nov 18, 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 71f07dc (Wed Dec 04 15:55:27 UTC 2019)

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

@flinkbot
Copy link
Collaborator

flinkbot commented Nov 18, 2019

CI report:

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

@tisonkun
Copy link
Member Author

@flinkbot run travis

@tisonkun tisonkun force-pushed the FLINK-14839 branch 2 times, most recently from e1f7257 to 30ef6bc Compare November 20, 2019 02:07
Copy link
Member

@GJL GJL left a comment

Choose a reason for hiding this comment

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

Looks ok. I have left some remarks.

@@ -352,8 +353,8 @@ public JobVertex findVertexByID(JobVertexID id) {
*
* @param paths paths of the directories/JAR files required to run the job on a task manager
*/
public void setClasspaths(List<URL> paths) {
classpaths = paths;
public void addClasspaths(Collection<URL> paths) {
Copy link
Member

Choose a reason for hiding this comment

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

Are we actually invoking addClasspaths multiple times? It seems that the changeset could be smaller by just adding a null check to the setter.

Copy link
Member Author

Choose a reason for hiding this comment

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

So for addJars. We don't call addJars multiple times for now. However, it fits the abstraction that we firstly instance an empty collection and then add member per call. If we still using setter and with a null checker the field cannot be final while we don't gain a lot from such mutability.

@tisonkun
Copy link
Member Author

@GJL could you give this patch another pass? I've addressed your comments above.

Copy link
Member

@GJL GJL left a comment

Choose a reason for hiding this comment

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

I am afraid that we cannot do this change. Let me know if you see a workaround.

@@ -100,7 +101,7 @@
private final List<PermanentBlobKey> userJarBlobKeys = new ArrayList<>();

/** List of classpaths required to run this job. */
private List<URL> classpaths = Collections.emptyList();
Copy link
Member

Choose a reason for hiding this comment

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

It's problematic that JobGraph implements Serialized and classpaths is a non-transient field. After a cluster upgrade to 1.10 addClasspaths will throw UnsupportedOperationException if classpath of the serialized JobGraph was previously empty.

Copy link
Member Author

Choose a reason for hiding this comment

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

OK I can see the problem. Although we can work around by adding another field and add some bridge code I don't it is worth to do so because this is just a nice to have improvement. A reasonable way in my mind is that we take this thing into consideration when we port JobGraph to its protobuf version if there will be one. Anyway, defer the effort until we are in a codebase easy to do it.

@tisonkun
Copy link
Member Author

closed as I cannot find a worthy workaround for the problem described in https://github.com/apache/flink/pull/10235/files/71f07dc72c9590bef027993dc258e598137514a7#r351205882

@tisonkun tisonkun closed this Nov 27, 2019
@tisonkun tisonkun deleted the FLINK-14839 branch November 27, 2019 11:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants