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-37187][doc] Add doc for Submitting Refresh Job of Materialized Table to Yarn/K8s #26073

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

Conversation

hackergin
Copy link
Contributor

What is the purpose of the change

Add doc for Submitting Refresh Job of Materialized Table to Yarn/K8s

Brief change log

  • Add doc for Submitting Refresh Job of Materialized Table to Yarn/K8s

Verifying this change

No need to verify as this pr only contains document change.

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, Kubernetes/Yarn, 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 Jan 24, 2025

CI report:

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

@@ -619,6 +619,65 @@ After execution, SQL Client will print the cluster id on the terminal. The scrip
<span class="label label-danger">Attention</span> When deploying a script to the cluster, SQL Client only supports running with `--jars` startup option, other options, e.g. `--init`
are not supported.

### Execute Materialized Table Refresh Jobs in Kubernetes/YARN

#### Execute Refresh Jobs in Session Mode
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: I suggest describing why a CREATE MATERIALIZED TABLE produces a refresh job, or pointing to the details here. Is there a consideration around whether the table exists or not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants