[followup](BE) rename assume_mutable to assert_mutable#63557
Conversation
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run buildall |
TPC-H: Total hot run time: 31496 ms |
TPC-DS: Total hot run time: 172016 ms |
|
/review |
There was a problem hiding this comment.
No blocking issues found. The PR is a focused mechanical rename of the COW API from assume_mutable* to assert_mutable*, with matching call-site, test, and BE core review-guide updates. I also verified there are no remaining assume_mutable references in tracked source files and git diff --check is clean.
Critical checkpoint conclusions:
- Goal/test: The rename matches the stated goal; existing COW ownership test was updated to the new API name.
- Scope: The change is small and focused; no behavioral change beyond diagnostics/name.
- Concurrency/lifecycle/config/compatibility: No new concurrency, lifecycle, configuration, storage format, or protocol compatibility concerns introduced.
- Parallel paths: Call sites across BE source and tests appear consistently renamed; no old API references remain in source.
- Error handling/data correctness/memory: The ownership assertion behavior is preserved, including throwing on shared ownership; no new memory ownership or data visibility changes.
- Tests: No new tests are needed for this mechanical rename; the existing COW exclusivity test remains present under the new API.
- Observability/performance: No runtime observability or performance impact expected.
User focus: No additional user-provided review focus was specified.
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
followup #63001. we changed the actual meaning of
assume_mutable