Starts the scheduler for the given Workflow.
Starts the scheduler for the given Workflow. Immediatly the scheduler will start interpreting the workflow and generate Executions sent to the provided Executor.
The jobs to run.
The executor to use to run the generated Executions.
The doobie transactor to use to persist the scheduler state if needed.
The logger to use to log internal debug state if neeed.
Provide a doobie SQL Fragment
used to retrieve all execution contexts from
the execution logs.
Provide a doobie SQL Fragment
used to retrieve all execution contexts from
the execution logs.
This fragment must be a SELECT query returning (id,json) tuples for all known scheduling contexts.
Returns a Json object containing the internal scheduler statistics informations.
Returns a Json object containing the internal scheduler statistics informations. These data will be send to the UI and can be used by the scheduler UI if needed.
Filter the statistics for the provided list of jobs.
A scheduler interpret a Workflow and instanciate Executions for all defined Jobs. For example, a typical cuttle Scheduler is the TimeSeries scheduler that executes the graph for each time partition.
The king of Scheduling managed by this Scheduler.