mirror of
https://github.com/monoscope-tech/monoscope.git
synced 2026-11-16 10:18:01 +00:00
Restore the boundary example: the TimeFusion bug it caught is fixed
It was quarantined as "not a product bug" on the strength of prod windows 2-3h and 25-26h back returning rows. Those read flushed parquet, which the bug never touched — consistent with it rather than counter-evidence. Only unflushed rows were hidden: a mem bucket advertised its ROUTING timestamp instead of the range of rows it held, so a batch spanning 21:00-23:00 reported max=21:00 and any `timestamp >= 21:30` pruned the whole bucket. Fixed in timefusion bf3abc8. Verified two ways against a TimeFusion carrying it: the same three-row batch that returned 0 for `>= 21:30` now returns 2, and this example passes. Kept because it is the only one that catches this class: it ingests several rows in one batch and then reads a window above the earliest. Single-row inserts make min == max per batch and hide it entirely.
This commit is contained in:
parent
71f9e2e6f2
commit
a21485f30d
1 changed files with 9 additions and 19 deletions
Loading…
Add table
Add a link
Reference in a new issue