I don't think there is a 1-1 migration path. Async operators supersede what Smart sensors were written to achieve - Cost Savings.
Smart Sensors were marked experimental feature for the same reason and there are currently just two Sensors that are Smart sensors compatible. The only thing I can currently think of is writing an async version of the Smart Sensor Hook and Operator differs based on the underlying library that is used and https://airflow.apache.org/docs/apache-airflow/stable/concepts/deferring.html explains how you can write one. Also - https://airflow.apache.org/docs/apache-airflow/stable/concepts/deferring.html#smart-sensors I believe we have done quite a bad job in the past assuming that our > users read all the discussions and AIPs we write. They don't. They > need some guidance. Which instances? I am just curious to know what are those bad instances where we "assumed" that our users read mailing list and not covered it in UPDATING.md or docs. Regards, Kaxil On Thu, Dec 9, 2021 at 3:46 PM Jarek Potiuk <[email protected]> wrote: > Extremely good point Tomek. > > Also as Ephraim pointed out in the PR - IMHO any time when we do > deprecation we should have a note in our docs, explaining at the very > least how the users should approach the migration as correctly pointed > out by @turbaszek in the devlist. > I think this should be a standard of any deprecation we do. > > I believe we have done quite a bad job in the past assuming that our > users read all the discussions and AIPs we write. They don't. They > need some guidance. > > J. > > On Wed, Dec 8, 2021 at 11:44 PM Tomasz Urbaszek <[email protected]> > wrote: > > > > Do we have documentation about how to migrate from smart sensors to > deferrable operators? >
