Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Make resources available to sensors
See original GitHub issueUse Case
If a certain row appears in our database, a pipeline run should be executed. This needs to be checked every 5 minutes. Checking the table requires a authenticated database client, which is already existing and used by the same pipeline, it handles authentication during initialization.
Ideas of Implementation
Just take the resource which is given to the pipeline (depending on the mode) and make it available with the required_resource_keys like it’s done with the solids.
Additional
Thank you and keep up the good work guys, I really like to work with dagster.
Message from the maintainers:
Excited about this feature? Give it a 👍. We factor engagement into prioritization.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:32
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
A really good request. Most of sensors watch external resources (APIs, S3 buckets, DBs, queues) to trigger pipeline. It would be nice to configure external resources for solids and sensors in the same way. It will also make unit testing and mocking more consistent
Another request in slack https://dagster.slack.com/archives/C01U954MEER/p1650312986241359