Skip to content

branch-4.1: [fix](fe) Fix NereidsCoordinator not created in proxy flow due to missing parsedStatement on StatementContext #64363#64437

Open
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-64363-branch-4.1
Open

branch-4.1: [fix](fe) Fix NereidsCoordinator not created in proxy flow due to missing parsedStatement on StatementContext #64363#64437
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-64363-branch-4.1

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Cherry-picked from #64363

…sing parsedStatement on StatementContext (#64363)

Problem Summary:

In a multi-FE environment, when a CREATE TABLE AS SELECT with recursive
CTE is forwarded from a follower FE to the master FE, the execution
fails with "fragment has no children".

Root Cause: 
In the proxy flow (ConnectProcessor.proxyExecute() →
StmtExecutor(ConnectContext, OriginStatement, boolean)), the
StatementContext is created fresh without a parsedStatement. When
parseByNereids() later parses the SQL, it only sets this.parsedStmt on
the StmtExecutor but did not propagate it to the ConnectContext's
StatementContext.

This caused SessionVariable.canUseNereidsDistributePlanner() to return
false (because statementContext.getParsedStatement() instanceof
LogicalPlanAdapter checked against null), which led to two consequences:

NereidsPlanner.distribute() skipped generating Nereids distributed plans
EnvFactory.createCoordinator() created a legacy Coordinator instead of
NereidsCoordinator
The legacy Coordinator cannot handle Nereids-planned fragments without
distributed plans, resulting in "fragment has no children" at
Coordinator.findMaxParallelFragmentIndex().

Fix:
In StmtExecutor.parseByNereids(), after parsing the SQL, propagate the
parsed statement to the ConnectContext's StatementContext via
this.context.getStatementContext().setParsedStatement(parsedStmt). This
ensures consistency with what downstream code
(canUseNereidsDistributePlanner) reads.
@github-actions github-actions Bot requested a review from yiguolei as a code owner June 12, 2026 02:08
@hello-stephen

Copy link
Copy Markdown
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@hello-stephen

Copy link
Copy Markdown
Contributor

run buildall

@hello-stephen

Copy link
Copy Markdown
Contributor

FE UT Coverage Report

Increment line coverage 100.00% (2/2) 🎉
Increment coverage report
Complete coverage report

@hello-stephen

Copy link
Copy Markdown
Contributor

FE Regression Coverage Report

Increment line coverage 0.00% (0/2) 🎉
Increment coverage report
Complete coverage report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants