Closed peterdudfield closed 2 months ago
One to think about @devsjc
I feel like this is one for the dag not the consumer - especially if all the various data import jobs are meant to update the table, one could envisage a task at the end of each relevant dag
yea, I'll try and write something and see how neat it looks in the dag
Seems like less code duplication and seperation that way as well - one reuseable task vs several individual implementations in seperate microservices.
Ill close this for now, as we do update this through the API now
Detailed Description
How to update the
input_data_last_updated
once a consumer has run.Context
input_data_last_updated
. see herePossible Implementation
dag
to get it to do this, would need to give it DB_URL access