Mryange opened a new pull request, #69359:
URL: https://github.com/apache/doris/pull/69359

   ### What problem does this PR solve?
   
   Issue Number: N/A
   
   Related PR: #67738
   
   Problem Summary:
   
   Backport #67738 to branch-4.1. Recursive CTE queries can fail with missing 
fragment contexts or rerunnable parameters. Root cause: duplicate reset 
requests and materialized ordinary CTE producers shared by independent 
recursive controllers. Deduplicate reset entries by fragment ID and BE address, 
and inline transitive dependencies of recursive CTEs.
   
   Resolve the CTEInlineTest conflict by adding the test table and imports 
required by the new test, without backporting the unrelated CTE pruning changes 
from #62828.
   
   ### Release note
   
   Fix recursive CTE failures caused by duplicate fragment resets and shared 
materialized CTE dependencies.
   
   ### Check List (For Author)
   
   - Test
       - [ ] Regression test
       - [ ] Unit Test
       - [ ] Manual test
       - [ ] No need to test or manual test
   
   FE unit and regression coverage are included in the backport. Compilation 
and tests have not been run for this backport. Diff whitespace checks passed 
with the original generated output's trailing blank line preserved.
   
   - Behavior changed:
       - [ ] No.
       - [x] Yes. Ordinary CTEs transitively referenced by recursive terms are 
inlined.
   
   - Does this need documentation?
       - [x] No.
       - [ ] Yes.
   
   ### Check List (For Reviewer who merge this PR)
   
   - [ ] Confirm the release note
   - [ ] Confirm test cases
   - [ ] Confirm document
   - [ ] Add branch pick label
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to