-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[refactor] (Nereids) rename GroupExpression.getParent() to getOwnerGroup() #11027
Conversation
please use |
// TODO: need to merge group recursively | ||
groupExpression.getParent().removeGroupExpression(groupExpression); | ||
GroupExpression that = groupExpressions.get(groupExpression); | ||
mergeGroup(groupExpression.getOwnerGroup(), that.getOwnerGroup()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should add some ut for merge group recursively
wait for checks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
…oup() (apache#11027) GroupExpression.getParent() returns the group which contains this expr. This name is missleading especially in tree structures. So we change the name to getOwnerGroup.
…oup() (apache#11027) GroupExpression.getParent() returns the group which contains this expr. This name is missleading especially in tree structures. So we change the name to getOwnerGroup.
…oup() (apache#11027) GroupExpression.getParent() returns the group which contains this expr. This name is missleading especially in tree structures. So we change the name to getOwnerGroup.
Proposed changes
GroupExpression.getParent() returns the group which contains this expr. This name is missleading especially in tree structures.
So we change the name to getOwnerGroup.
@924060929 could u review, please?
Issue Number: close #xxx
Problem Summary:
Describe the overview of changes.
Checklist(Required)
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...