Skip to content

branch-4.1: [refactor](nereids) Remove the PLAN REPLAYER PLAY command - #67147

Merged
yiguolei merged 1 commit into
apache:branch-4.1from
CalvinKirs:backport-66817-branch-4.1
Aug 26, 2026
Merged

branch-4.1: [refactor](nereids) Remove the PLAN REPLAYER PLAY command#67147
yiguolei merged 1 commit into
apache:branch-4.1from
CalvinKirs:backport-66817-branch-4.1

Conversation

@CalvinKirs

Copy link
Copy Markdown
Member

### What problem does this PR solve?

Issue Number: None

Related PR: apache#66817

Problem Summary: PLAN REPLAYER PLAY was a developer-only command for replaying a minidump on another FE and has no known users. Remove its lexer and parser alternatives, runtime loading and comparison logic, offline runner, and FE packaging. PLAN REPLAYER DUMP remains unchanged, while play becomes available as an ordinary identifier.

### Release note

Remove the PLAN REPLAYER PLAY statement and the packaged minidump/nereids_ut.sh offline runner. PLAN REPLAYER DUMP is unchanged.

### Check List (For Author)

- Test: Manual test (bash -n build.sh and diff/reference checks passed; ./run-fe-ut.sh --run org.apache.doris.nereids.parser.NereidsParserTest was attempted twice, but the host killed Maven with exit 137 during compilation before test execution; ANTLR generation and Maven checkstyle passed in both attempts)

- Behavior changed: Yes (PLAN REPLAYER PLAY is removed and play is now an ordinary identifier; PLAN REPLAYER DUMP is unchanged)

- Does this need documentation: No
@CalvinKirs
CalvinKirs requested a review from yiguolei as a code owner August 26, 2026 03:30
@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?

@CalvinKirs

Copy link
Copy Markdown
Member Author

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

@yiguolei
yiguolei merged commit 5e4fead into apache:branch-4.1 Aug 26, 2026
29 of 32 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

PR approved by anyone and no changes requested.

@github-actions github-actions Bot added the approved Indicates a PR has been approved by one committer. label Aug 26, 2026
@github-actions

Copy link
Copy Markdown
Contributor

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

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

Labels

approved Indicates a PR has been approved by one committer. reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants