ezmsg.baseproc.util.pipeline_settings.INIT_FINAL_COMPONENT_ADDRESS#
- INIT_FINAL_COMPONENT_ADDRESS: Final[str] = '__init_final__'#
Sentinel
component_addressvalue attached to the finalPipelineSettingsEventof the startup snapshot. Producers emit one such event withevent_type=INITIAL,structured_value=Noneandrepr_value=""immediately after the last per-component INITIAL has been queued. Consumers that need to aggregate the per-component initial snapshot (e.g., a typed-column sink that wants one merged row instead of N rows + N-1 schema-driven rotations) detect this sentinel by address and flush their pending buffer at that point. Sinks that don’t need aggregation should treat the sentinel as a control message — by default,PipelineSettingsEvent.flatten_for_table()returnsNonefor the sentinel so JSON-row sinks naturally skip it.