gopidesupavan commented on issue #39593: URL: https://github.com/apache/airflow/issues/39593#issuecomment-2248378000
> @gopidesupavan Yes, ideally we use the best possible way to run a sensor, which should be async implementation on Triggerer. If triggerer isn't available, it can fallback to poke or reschedule on the worker but at least it should default to most efficient usage without users having to mention it. But feel free to create your proposal on what you think is the best option > > > Hi @kaxil > > Over the past few days, I've thoroughly examined the core codebase and now have a strong grasp of the sensor component. I've also been contributing to Airflow for several months. > > I would like to further explore the core areas. I feel like this is a great opportunity at this point. > > Could you please throw some light on what the expectation on this `Change sensors to use async by default`? > > In confluence it is mentioned. https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+3+Workstreams Sensor Improvements about sensor modes. > > `Remove poke/reschedule mode from sensors` > > But here in above it mentioned `remove poke mode`. > > Is it removing both modes and keeping completely default always with async? > > Appreciate your help 😄 .. > > And not sure if anyone else is already working on this. am happy to contribute other areas also 😄 Thank you @kaxil, Sure have couple of things i am thinking , will draft my proposal and send it for review soon. -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
