-
Notifications
You must be signed in to change notification settings - Fork 4
Integrate callback and sla #454
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
Conversation
…_callback_and_sla
| return me.ToErr() | ||
| } | ||
|
|
||
| func (s *JobRunService) createOperatorRun(ctx context.Context, event *scheduler.Event, operatorType scheduler.OperatorType) error { |
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 could have kept create operator run & register sla's independent we don't need to keep them in a same function.
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 we can do this, logically right
| return err | ||
| } | ||
|
|
||
| if existingOperatorRunState == nil || *existingOperatorRunState != scheduler.StateRetry { |
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.
In my opinion we should see this whole operation as two sub functions fetchAllSLAAlertConfigs & Registration.
| return err | ||
| } | ||
|
|
||
| switch event.Type { |
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.
same things can be done here as well
* fix: enrich event context in airflow callbacks --------- Co-authored-by: Yash Bhardwaj <[email protected]>
No description provided.