-
Notifications
You must be signed in to change notification settings - Fork 15.2k
Add direct-to-triggerer for DataprocSubmitJobOperator #52005
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
base: main
Are you sure you want to change the base?
Add direct-to-triggerer for DataprocSubmitJobOperator #52005
Conversation
query = session.query(TaskInstance).filter( | ||
TaskInstance.dag_id == self.task_instance.dag_id, | ||
TaskInstance.task_id == self.task_instance.task_id, | ||
TaskInstance.run_id == self.task_instance.run_id, | ||
TaskInstance.map_index == self.task_instance.map_index, | ||
) | ||
task_instance = query.one_or_none() |
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.
This code will not be compatible with AF3. If you were looking for solutions for this functionality, I think it is better to use already existing trigger. If I understand correctly. Can you please show also your system tests results for this code, both for AF2 and AF3 as screenshots? thanks
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.
Thank you for reviewing.
Actually when i ran system test, it failed so that i should fix the code. And i can't find ref about why the code that you mentioned couldn't be compatible with AF3. Could you give me ref for that?
close: #50563
Hi i implemented
start_from_trigger
function for DataprocSubmitJobOperator. Pls review my pr