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-35194][table] Support describe job with job id #24728
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@xuyangzhong Thanks for your contribution, I left some comments. BTW, can you help to open a jira ticket to finish the doc of desc job syntax.
...ateway/src/main/java/org/apache/flink/table/gateway/service/operation/OperationExecutor.java
Outdated
Show resolved
Hide resolved
...ateway/src/main/java/org/apache/flink/table/gateway/service/operation/OperationExecutor.java
Outdated
Show resolved
Hide resolved
...er/src/main/java/org/apache/flink/table/planner/operations/SqlNodeToOperationConversion.java
Outdated
Show resolved
Hide resolved
new IllegalStateException( | ||
"Test job " + jobId + " not found.")); | ||
assertThat(jobRow.getString(1)).hasToString(pipelineName); | ||
assertThat(jobRow.getString(2)).hasToString("RUNNING"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The job status always beRUNNING
here? maybe it has finished? My concern is whether it causes an unstable test?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it's always RUNNING, because ExecutionOptions.RUNTIME_MODE
is streaming default.
assertThat(jobRow.getString(2)).hasToString("RUNNING"); | ||
assertThat(jobRow.getTimestamp(3, 3).getMillisecond()) | ||
.isBetween(timeOpStart, timeOpSucceed); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do need we cancel the job manually after getting the job status?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, all jobs will be cancelled automatically. You can find more details at MiniClusterExtension#afterAll
.
The doc jira is: https://issues.apache.org/jira/browse/FLINK-35271 |
What is the purpose of the change
Support syntax '{ DESCRIBE | DESC } JOB 'xxx''
Brief change log
Verifying this change
Tests are added to verify it.
Does this pull request potentially affect one of the following parts:
@Public(Evolving)
: noDocumentation