-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Bmoric/migrate existing schedule #9076
Conversation
a22b4c8
to
0851a27
Compare
…rate-existing-schedule
@@ -188,6 +197,16 @@ public static ServerRunnable getServer(final ServerFactory apiFactory, final Con | |||
configs.getWorkspaceRoot(), | |||
configs.getAirbyteVersionOrWarning(), | |||
featureFlags); | |||
final JobNotifier jobNotifier = new JobNotifier( |
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.
we can shift this down to only be created inside the featureFlags.usesNewScheduler
block.
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.
Approving since it's looks similar to what we discussed.
I'm not extremely familiar with edge cases on the new scheduler, so I would also want @jrhizor to double confirm this works.
…rate-existing-schedule
What
This is migrating existing connection to the new scheduler. It refrain from migrating a connection that have already be migrated.
closes #8546