-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
Add processor_subdir to import_error table to handle multiple dag processors #35956
Conversation
4d1d6c1
to
5865dda
Compare
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.
LGTM. @mhenc ? Maybe you would like to review/comment ?
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.
Looks good. Thank you for the fix!
The other issue we had on switching from one dag processor to multiple ones using subdir was that old import errors were not deleted as they had different directory. It will be the same issue on switching to single dag processor from subdir based approach and needs a one time cleanup of import error table. Just noting this down if anyone encounters it. |
Took me a while to find this PR and specifically your comment above @tirkarthi , but thank you for noting this behavior! Made for an easy fix and understanding of how this occurred on a client's airflow deployment 🖖 |
Add processor_subdir to import_error table to update the value while creating ImportError entry. Use the processor_subdir to filter for ImportError entries that belong to the current dag processor.
closes: #35949
related: #35949