Channels
pacc-may-31-2023
prefect-ai
pacc-clearcover-june-12-2023
marvin-in-the-wild
data-ecosystem
geo-israel
geo-japan
prefect-cloud
ppcc-may-16-2023
prefect-azure
prefect-docker
prefect-recipes
gratitude
geo-nyc
geo-bay-area
geo-boston
geo-london
geo-dc
geo-chicago
geo-berlin
geo-texas
geo-seattle
geo-colorado
prefect-community
data-tricks-and-tips
prefect-aws
prefect-gcp
introductions
find-a-prefect-job
prefect-dbt
random
events
ask-marvin
show-us-what-you-got
prefect-getting-started
prefect-integrations
prefect-contributors
best-practices-coordination-plane
announcements
prefect-server
prefect-ui
prefect-kubernetes
Title
g
Gustavo Frederico
05/06/2022, 1:55 AMAirflow, for instance, have Sensors. Sensors wait for something external to happen.
k
Kevin Kho
05/06/2022, 2:29 AMWe don’t have sensors, but you could put the polling logic inside a task or a flow. Or you can make the event trigger the flow like i mentioned above
g
Gustavo Frederico
05/06/2022, 2:32 AMI suppose that is not as good as exposing blocking tasks as REST endpoints. I’ll need to find another product. I see that Google Workflows have callbacks ( https://cloud.google.com/workflows/docs/creating-callback-endpoints ) . It’s unfortunate that Prefect doesn’t have this.
a
Anna Geller
05/06/2022, 10:15 AM@Gustavo Frederico we have a detailed walkthrough about how you can approach it here
Prefect provides several methods of approaching that problem, even if we don't call it sensors. Happy to answer your questions about this orchestration pattern - what's the use case you tried to solve with sensors? Are you waiting for some files to arrive?