-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[Improve] Add custom job id arg in client #6943
Conversation
Thanks all, merged. |
new JobContext(isStartWithSavePoint ? jobId : jobClient.getNewJobId())); | ||
Long finalJobId; | ||
if (isStartWithSavePoint || jobId != null) { | ||
finalJobId = jobId; |
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.
@Hisoka-X hi, i relealize a problem, if user pass same job id with the running jobs, will it has issue?
now i story some status in IMAP by job id. if use same job id, the status maybe impact?
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, the key point is that the ID cannot be repeated, which currently needs to be ensured by the user
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.
Fix by #7021
Purpose of this pull request
This PR add a new param in
seatunnel.sh
named--set-job-id
. User can use this param to fix job id when submit job. Not generate by SeaTunnel. This usage can facilitate third-party integration of SeaTunnel.Does this PR introduce any user-facing change?
no
How was this patch tested?
add new test.
Check list
New License Guide
release-note
.