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-28617][SQL Gateway] Support stop job statement in SqlGatewayService #21292

Merged
merged 10 commits into from
Dec 18, 2022

Conversation

link3280
Copy link
Contributor

What is the purpose of the change

Support stop job statement in SqlGatewayService. Subtask of FLIP-222.

Brief change log

  • Support stop job statement in SqlGatewayService
  • Extend SqlGatewayServiceExtension to include a mini cluster for statement execution

Verifying this change

Please make sure both new and modified tests in this PR follows the conventions defined in our code quality guide: https://flink.apache.org/contributing/code-style-and-quality-common.html#testing

This change added tests and can be verified as follows:

(example:)

  • Added integration tests for stop job statements.

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? yes
  • If yes, how is the feature documented? not documented

@flinkbot
Copy link
Collaborator

flinkbot commented Nov 11, 2022

CI report:

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

@link3280
Copy link
Contributor Author

The CI failed due to an unrelated Kafka connector test. We may take a look at the codes first. cc @fsk119

@link3280
Copy link
Contributor Author

@flinkbot run azure

2 similar comments
@link3280
Copy link
Contributor Author

@flinkbot run azure

@link3280
Copy link
Contributor Author

@flinkbot run azure

@link3280
Copy link
Contributor Author

Rebased on the recent master to see if the test failure still exists.

@link3280
Copy link
Contributor Author

ping @fsk119

Copy link
Member

@fsk119 fsk119 left a comment

Choose a reason for hiding this comment

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

Sorry for the late response. I left some comments.

@link3280
Copy link
Contributor Author

@flinkbot run azure

Copy link
Member

@fsk119 fsk119 left a comment

Choose a reason for hiding this comment

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

Thanks for your update.

@link3280
Copy link
Contributor Author

link3280 commented Dec 17, 2022

Updated as suggested. CI turns green. cc @fsk119

Copy link
Member

@fsk119 fsk119 left a comment

Choose a reason for hiding this comment

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

LGTM

Comment on lines +460 to +468
} catch (Exception e) {
throw new FlinkException(
"Could not stop job "
+ stopJobOperation.getJobId()
+ " in session "
+ operationHandle.getIdentifier()
+ ".",
e);
}
Copy link
Member

Choose a reason for hiding this comment

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

nit: It's a little trivial to catch the same exception twice with a similar msg. In the next PR, we can remove this.

@fsk119 fsk119 merged commit 934edd3 into apache:master Dec 18, 2022
chucheng92 pushed a commit to chucheng92/flink that referenced this pull request Feb 3, 2023
akkinenivijay pushed a commit to krisnaru/flink that referenced this pull request Feb 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants