You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 87a8d55
Browse filesBrowse the repository at this point in the historyBrowse files
[fix](ivm) Net canceled deletes in MIN/MAX extreme counts
When the old extreme is NULL, the insert-side extreme became the new
extreme but its stored count ignored deletes emitted for the same value by
the same join refresh. The inflated MIN_COUNT/MAX_COUNT could later keep a
deleted extreme instead of falling back. Initialize the count from the net
insert/delete contributions at the selected extreme, and keep the complete
refresh fallback when the surviving count cannot be proved.
Key changes:
- Compute the old-NULL count as insert count minus matching delete count; fall back when a delete is closer to the extreme or cancels every inserted row.
- Add the MIN/MAX beyond-insert comparison and cover the net-count expression in the FE processor tests.
- Fix the BE merge fixture to expect the two merged minima.
- Make both MIN/MAX count regression suites wait for a task id distinct from the previous refresh.
Unit Test:
- IvmAggMinProcessorTest, IvmAggMaxProcessorTest, IvmAggDeltaHandlerTest, IvmNormalizeUniqKeysMTMVTest
- regression-test: mtmv_p0/ivm test_ivm_minmax_count, test_ivm_minmax_count_join
0 commit comments