Repository navigation
fix(engine): bound table gap analysis memory, analyse expression columns - #549
Merged
ivanmiletic merged 2 commits intoOct 20, 2026
Merged
Conversation
Missing-case detection built the full atom/row partition for every column before charging the work budget. Nested ranges (`> 1`, `> 2`, ...) make that partition quadratic, so large tables (tens of thousands of rows) allocated gigabytes before giving up, exhausting the 1GB WASM memory. The partition size is now counted first and the budget checked before building it; results are unchanged (50k rows: ~10GB/28s -> ~650MB/1s natively). Columns without a field whose filled cells are all conditions on one field (`age > 50`, `age > 30`) are now analysed like field columns on that field: duplicates, unreachable rows, missing cases and compression. Compressed and missing-case cells are written back as full expressions (`age > 30`). Columns mixing fields or using non-analysable expressions stay opaque.
stefan-gorules
approved these changes
Oct 20, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Missing-case detection built the full atom/row partition for every column before charging the work budget. Nested ranges (
> 1,> 2, ...) make that partition quadratic, so large tables (tens of thousands of rows) allocated gigabytes before giving up, exhausting the 1GB WASM memory. The partition size is now counted first and the budget checked before building it; results are unchanged (50k rows: ~10GB/28s -> ~650MB/1s natively).Columns without a field whose filled cells are all conditions on one field (
age > 50,age > 30) are now analysed like field columns on that field: duplicates, unreachable rows, missing cases and compression. Compressed and missing-case cells are written back as full expressions (age > 30). Columns mixing fields or using non-analysable expressions stay opaque.