Skip to content

branch-4.1: [fix](regression) stabilize colocate column order plan test #64940 - #65315

Merged
yiguolei merged 1 commit into
branch-4.1from
auto-pick-64940-branch-4.1
Jul 13, 2026
Merged

branch-4.1: [fix](regression) stabilize colocate column order plan test #64940#65315
yiguolei merged 1 commit into
branch-4.1from
auto-pick-64940-branch-4.1

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Cherry-picked from #64940

## Proposed changes
Pin `parallel_pipeline_task_num=1` in the three-table
`test_colocate_join_of_column_order` explain query.
The case already waits for `group_column_order3` to become stable, but
Cloud P0 history still shows intermittent `HAS_COLO_PLAN_NODE: false` /
`INNER JOIN(PARTITIONED)` after the wait. The detailed failures share
the same plan shape: the first join is planned as a partitioned shuffle,
so its output no longer keeps the `NATURAL` hash distribution needed by
the second join's colocate check.
This is driven by physical-plan selection rather than statistics
readiness. One sampled failure already executed `ALTER TABLE ... SET
STATS` and still produced the same `INNER JOIN(PARTITIONED)` plan.
Pinning `parallel_pipeline_task_num=1` removes the bucket-shuffle
downgrade nondeterminism while preserving the original colocate planner
coverage.
@github-actions
github-actionsBot requested a review from yiguolei as a code ownerJuly 7, 2026 08:15
@yiguolei

Copy link
Copy Markdown
Contributor

run buildall

@yiguoleiyiguolei reopened this Jul 13, 2026
@github-actions

Copy link
Copy Markdown
ContributorAuthor

PR approved by at least one committer and no changes requested.

@github-actionsgithub-actionsBot added the approved Indicates a PR has been approved by one committer. label Jul 13, 2026
@github-actions

Copy link
Copy Markdown
ContributorAuthor

PR approved by anyone and no changes requested.

@yiguolei
yiguolei merged commit 6f764ee into branch-4.1Jul 13, 2026
41 of 46 checks passed
@morrySnow
morrySnow deleted the auto-pick-64940-branch-4.1 branch August 20, 2026 04:05
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approvedIndicates a PR has been approved by one committer.reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@yiguolei@shuke987