Skip to content

ScheduledMerges: also test nested unions and arbitrary configs#814

Open
mheinzel wants to merge 4 commits intomainfrom
mheinzel/prototype-tests-nested-union
Open

ScheduledMerges: also test nested unions and arbitrary configs#814
mheinzel wants to merge 4 commits intomainfrom
mheinzel/prototype-tests-nested-union

Conversation

@mheinzel
Copy link
Collaborator

Description

We had already noted that testing nested unions (unions of tables that are themselves result of a union) would be a good idea. Also, after making some LSM parameters configurable in #716, it seems sensible to test more than just the default values.

As a preparation for further changes to the prototype, this PR addresses these points and makes small improvements to the invariants and properties we assert.

@mheinzel mheinzel force-pushed the mheinzel/prototype-tests-nested-union branch from 458fbf9 to dabce7d Compare February 16, 2026 13:18

-- | For simplicity, this is not a recursive structure. We just nest once, or
-- not at all if there is just a single 'UnionInput'.
type NestedUnionInput = QC.NonEmptyList UnionInput
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It could cover even more corner cases if we also made some inserts to the child unions before unioning them again (so they have regular levels in addtiion to the union level). Wouldn't be terribly complicated, but I wasn't sure whether it's worth it, since we still have the lockstep tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant