sri raghavan03/14/2023, 7:53 PM
• per-tenant configuration that lives in our production DB (RDS), and determines the timezone for each tenant, and how long to wait after midnight in that timezone before the run for a given day can be started We're currently thinking to use a single sensor, that checks frequently (in a relatively tight evaluation loop) whether or not each tenant is ready to 'advance' to the next day. I don't think Dagster has support for "partitioned cursors", though, which is the amount of state I imagine we'd need to track this. Ideas?
claire03/16/2023, 10:40 PM
to update the cursor after evaluation.
sri raghavan03/17/2023, 2:02 AM
claire03/17/2023, 4:48 PM