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

[INLONG-10436][Manager] Move schedule configuration from stream to group #10437

Merged
merged 4 commits into from
Jun 18, 2024

Conversation

aloyszhang
Copy link
Contributor

@aloyszhang aloyszhang commented Jun 17, 2024

Fixes #10436

Motivation

#9865 Support submits a Flink job for offline sync, and the schedule status is saved with an inlong stream.
But for the real-time sync job, there is only one stream in a group(one Flink job one stream), to keep consistency, we should keep the schedule information at the group level.

Modifications

  1. remove schedule register status in stream ext info
  2. add schedule register status in group ext info
  3. fix the package path error in manager-schedule module, from org.apache.inlong.schedule to org.apache.inlong.manager.schedule

Verifying this change

(Please pick either of the following options)
covered by org.apache.inlong.manager.service.workflow.group.CreateGroupWorkflowDefinitionTest.java

Documentation

  • Does this pull request introduce a new feature? (no)

@aloyszhang aloyszhang self-assigned this Jun 17, 2024
@aloyszhang aloyszhang requested a review from fuweng11 June 17, 2024 10:53
@dockerzhang dockerzhang changed the title [INLONG-10436][Manager] move scheudle configuration from stream to group [INLONG-10436][Manager] Move schedule configuration from stream to group Jun 17, 2024
@dockerzhang dockerzhang merged commit 8a6a490 into apache:dev-offline-sync Jun 18, 2024
10 checks passed
aloyszhang added a commit to aloyszhang/inlong that referenced this pull request Jul 9, 2024
aloyszhang added a commit to aloyszhang/inlong that referenced this pull request Jul 9, 2024
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.

3 participants