slt: Add null-aware mark join tests for current behavior#22981
Open
AdamGS wants to merge 1 commit into
Open
Conversation
Signed-off-by: Adam Gutglick <adamgsal@gmail.com>
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
1 participant
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.
Which issue does this PR close?
Rationale for this change
Taken out of #21585 to make it easier to review.
What changes are included in this PR?
Adds
null_aware_mark_join.sltfile that includes many examples of queries using null-aware mark joins. I've collected them both from other existing tests, theStory of Join (in HyPer)paper and some help from Codex.These tests currently pass as they ensure the wrong behavior. Once the original PR (or parts of it) get merged, more tests can be changed to assert the correct behavior.
Are these changes tested?
Verified locally
Are there any user-facing changes?
No