basantjamwal commented on issue #77021: URL: https://github.com/apache/airflow/issues/77021#issuecomment-6855911332
Hi @stephen-bracken, I'd like to pick this up — quick notes before I start. The reason overrides don't survive a clear today is `refresh_from_task` — it resets the task back to whatever's in the DAG file every time. There's a related proposal, AIP-117, solving basically the same "override surviving a clear" problem for pool/priority fields — might be worth reusing that mechanism here instead of building a new one. Airflow 3.1 also added `run_on_latest_version` for clear-time DAG version selection, which is a decent reference for how a new clear-time option gets wired into the API + UI. Question: should this build on AIP-117, or is it a separate thing? If that's fine, here's roughly what I'd do, kept small on purpose: - Start with one operator (e.g. HttpOperator's endpoint), not all of them - Store the override so it survives refresh_from_task - Only allow overriding fields already in that operator's template_fields - Add it to the clearTaskInstances API - Add a matching input in the Clear Task UI so it's not API-only Won't start coding till I hear back — let me know if this seems like the right direction. -- 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]
