aeroyorch commented on PR #65932: URL: https://github.com/apache/airflow/pull/65932#issuecomment-4379304790
> > So my understanding is that dynamically modifying some scheduling options per try is still expected Airflow behavior, and not something considered legacy or unintended. Is that correct? I just want to confirm that I am not trying to fix behavior that we actually want to move away from. > > Yeah, you are correct - it's documented somewhere (or at least not unheard of in the wild) to do things like "on the second attempt, put this in to a high priority queue" etc. And yes, we want to continue supporting that. Ok, thanks. One additional follow-up: with `refresh_from_task` now running at the retry transition, a buggy hook or `PriorityWeightStrategy` will raise and wedge the retry. Worth catching and sending the TI to FAILED with a loud log, or does a different approach make more sense? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
