You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
### What problem does this PR solve?
Issue Number: None
Related PR: apache#67328
Problem Summary: Follow-up review found that atomic OUTFILE finalization could use the wrong Nereids deadline, contact old BEs, publish the marker before all receiver commits, miss late cleanup and shutdown races, and regress local or multipart durability. Keep the protocol version-gated, order the global decision before marker and client publication, and preserve bounded rollback ownership during the live query lifecycle.
### Release note
None
### Check List (For Author)
- Test: Unit Test
- BE ASAN unit tests: 36/36 passed.
- FE unit tests: 4/4 passed with Checkstyle and source/test compilation.
- Build hygiene and clang-format 16 checks passed.
- Clang-tidy was attempted but could not analyze the existing tree because of unrelated toolchain and header diagnostics.
- Behavior changed: Yes. Supported execution versions publish OUTFILE success only after every receiver commits; older versions retain the legacy path.
- Does this need documentation: No
0 commit comments