Add semi and cross semi join kind #8263
Merged
Conversation
This file contains 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
ti-chi-bot
bot
added
release-note-none
size/L
|
/run-all-tests |
gengliqi
force-pushed
the
add-semi-join-type
branch
from
9ecfadb
to
15d469a
Compare
|
/run-all-tests |
1 similar comment
|
/run-all-tests |
ti-chi-bot
bot
added
size/XL
gengliqi
force-pushed
the
add-semi-join-type
branch
from
be2df2b
to
4560d99
Compare
|
/run-all-tests |
|
/run-all-tests |
Signed-off-by: gengliqi <gengliqiii@gmail.com>
|
/run-all-tests |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: windtalker, yibin87 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
[LGTM Timeline notifier]Timeline:
|
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.
What problem does this PR solve?
Issue Number: ref #8262
Problem Summary:
What is changed and how it works?
In the current implementation, the semi join without other conditions is marked by
inner joinandstrictness: any. The one with other conditions is marked byinner joinandstrictness: all && original_strictness: any.It is really confusing so I add the semi and cross semi join kind to separate semi join and inner join.
Check List
Tests
Side effects
Documentation
Release note