[CALCITE-3819] Prune parent RelNode when merging child RelSet with parent RelSet#1829
Merged
Conversation
hsyuan
added
LGTM-will-merge-soon
…rent RelSet Suppose we have 2 RelSets: RelSet A: rel1 RelSet B: rel2 rel1 is the parent of rel2. If there is a transformation rule that transform rel1 to rel2, we will merge RelSet A and B. During merge process, we can safely prune rel1 to avoid further rule apply on rel1 and reduce search space, more importantly, avoid cyclic reference.
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.
Suppose we have 2 RelSets:
RelSet A: rel1
RelSet B: rel2
rel1 is the parent of rel2.
If there is a transformation rule that transform rel1 to rel2, we will merge
RelSet A and B. During merge process, we can safely prune rel1 to avoid further
rule apply on rel1 and reduce search space, more importantly, avoid cyclic
reference.