Nextdoor/ndscheduler

Stronger sql model needed

tschm opened this issue · 3 comments

tschm commented

Your schema is weak. Can you please make sure job_id is a proper foreign key and you also include a definition for the job. Next, it all falls over once a job is deleted that still has relatives in the Executions table... Btw: I would recommend to use Pony for the job

@tschm - Could you open a PR with your suggested changes, perhaps? I just hope someone would review, and merge your changes in a timely manner :)

tschm commented

@kartick Very sorry. I have moved production/scheduling to apache airflow. Unfortunately I have no free capacities to address the points I have mentioned.

Understandable @tschm. It is a pretty complete solution. I looked at that as well (and Luigi) and settled for NDS for our use case.