Tracking issue for correctness bugs where a component assumes an aggregation's AggregationConfig (window shape, grouping, etc.) is stable for the lifetime of its stored data, but update_streaming_config can swap it at runtime (called by main.rs whenever the planner fires) with no purge of data written under the previous config.
The general hazard: any aggregation_id can have data spanning multiple different config "eras" in the store simultaneously (old-shaped data not yet evicted by retention, mixed with new-shaped data), and any code path that reads the current config to interpret historical stored data is at risk of silently misreading, dropping, or misattributing that old data.
Known instances
Scope
Add further instances here as found. Not all of these may need the same fix -- some may be narrow enough to patch locally, others may point at a shared root cause (e.g. versioning the stored shape per epoch) worth solving once.
Tracking issue for correctness bugs where a component assumes an aggregation's
AggregationConfig(window shape, grouping, etc.) is stable for the lifetime of its stored data, butupdate_streaming_configcan swap it at runtime (called bymain.rswhenever the planner fires) with no purge of data written under the previous config.The general hazard: any
aggregation_idcan have data spanning multiple different config "eras" in the store simultaneously (old-shaped data not yet evicted by retention, mixed with new-shaped data), and any code path that reads the current config to interpret historical stored data is at risk of silently misreading, dropping, or misattributing that old data.Known instances
scan_windows_via_exact's window-grid walk uses the current config'swindow_size_ms/slide_interval_msto compute probe shape/grid, silently missing pre-reconfig data stored under a different shape.Scope
Add further instances here as found. Not all of these may need the same fix -- some may be narrow enough to patch locally, others may point at a shared root cause (e.g. versioning the stored shape per epoch) worth solving once.