[Colocate plan][Step1] Colocate join covers more situations

[EmmyMiao87]

Proposed changes

There are 4 steps in colocate plan: join, agg, sort and set operation.
This is the first step.

The old colocate join can only cover the case where the child is hash or scan.
In fact, as long as the child's data distribution meets the requirements,
no matter what the plan node on the child node is, a colocate join can be performed.

Types of changes

What types of changes does your code introduce to Doris?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)
• Code refactor (Modify the code structure, format the code, etc...)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have created an issue on (Fix Colocate plan #5589) and described the bug/feature there in detail. Later
• Compiling and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• If these changes need document changes, I have updated the document
• Any dependent changes have been merged

Further comments

document is comming

[EmmyMiao87]

Why change import order of LogManager?

The order of import should comply with http://doris.apache.org/master/zh-CN/developer-guide/fe-eclipse-dev.html#%E4%BB%A3%E7%A0%81%E6%9B%B4%E6%96%B0

[EmmyMiao87]

seems not need return null too many, may under code is better:

       if (this instanceof ScanNode && tupleIds.contains(tupleId)) {
            return (ScanNode) this;
        } else if (!(this instanceof ExchangeNode)) {
            for (PlanNode planNode : children) {
                ScanNode scanNode = planNode.getScanNodeInOneFragmentByTupleId(tupleId);
                if (scanNode != null) {
                    return scanNode;
                }
            }
        }
        return null;

changed

[EmmyMiao87]

the comment is same as line 570. just keep one is enough.

removed

[HappenLee]

LGTM

[morningman]

why add all?

[EmmyMiao87]

If it is a test, add all the backends belonging to this ip.

[morningman]

Why changing the name?

[EmmyMiao87]

Because the previous configuration name is colocate join. It only controls the colocate of the join.
Now this new configuration uniformly controls the colocate of all plan node.
So it would be too one-sided to call colocate join.

[morningman]

LGTM