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-36070][flink-runtime-web] Modifying web UI to adapt to Incremental JobGraph Generation #25804

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

yuchen-ecnu
Copy link
Contributor

What is the purpose of the change

  • Modify web ui to support job graph auto-refresh for Incremental JobGraph Generation.

Brief change log

  • Modify the web ui to display the incremental job graph and the unconverted stream node.
  • Add a new checkbox in the webui to select whether to display the unconverted stream node or not.

Verifying this change

This change is a frontend(UI) work and are not covered by tests.

Does this pull request potentially affect one of the following parts:

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

Documentation

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

Preview

image

@flinkbot
Copy link
Collaborator

flinkbot commented Dec 16, 2024

CI report:

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

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.

2 participants