From d5b8e5e61263a2cf7e36305b647fab3cd49c55b0 Mon Sep 17 00:00:00 2001 From: Seth Wiesman Date: Fri, 17 Jan 2025 13:15:47 -0600 Subject: [PATCH] manually correct subsource status from starting to running Subsources move from starting to running lazily once they see a record flow through, even though they are online and healthy. This has been repeatedly brought up as confusing by users. So now, if the parent source is running, and the subsource is starting, we override its status to running to relfect its healthy status. --- src/catalog/src/builtin.rs | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/src/catalog/src/builtin.rs b/src/catalog/src/builtin.rs index cdf91465563f0..90392b3369e38 100644 --- a/src/catalog/src/builtin.rs +++ b/src/catalog/src/builtin.rs @@ -3243,6 +3243,16 @@ pub static MZ_SOURCE_STATUSES: LazyLock = LazyLock::new(|| BuiltinV self_events.status <> 'ceased' AND parent_events.status = 'stalled' THEN parent_events.source_id + -- Subsources move from starting to running lazily once they see + -- a record flow through, even though they are online and healthy. + -- This has been repeatedly brought up as confusing by users. + -- So now, if the parent source is running, and the subsource is + -- starting, we override its status to running to relfect its healthy + -- status. + WHEN + self_events.status = 'starting' AND + parent_events.status = 'running' + THEN parent_events.source_id ELSE self_events.source_id END AS id_to_use FROM