bobhan1 opened a new pull request, #66172:
URL: https://github.com/apache/doris/pull/66172
### What problem does this PR solve?
Issue Number: N/A
Related PR: #65021
Problem Summary:
Backport #65021 to `branch-4.0`.
This adds the `enable_topn_lazy_mat_phase2_no_write_file_cache` session
variable. When enabled, remote cache misses during the second phase of TopN
lazy materialization are read without writing the fetched data into file cache,
while existing cache hits continue to be read locally. The backport keeps the
`branch-4.0` pipeline/segment layout, block type, and file-cache statistics
interfaces.
Validation:
- `./build.sh --be --fe --cloud -j100`
- `./run-be-ut.sh --run
--filter='MaterializationSharedStateTest.*:BlockFileCacheTest.get_downloaded_blocks_if_fully_covered_is_read_only:BlockFileCacheTest.cached_remote_file_reader_remote_only_on_miss:BlockFileCacheTest.fd_cache_remove:BlockFileCacheTest.fd_cache_evict'
-j40` (9 tests passed)
- `./run-regression-test.sh --run -d cloud_p0/cache -s
test_topn_lazy_mat_phase2_no_write_file_cache -g docker -runMode=cloud
-dockerSuiteParallel 1 -image baohan-doris-regression:pr65021-4.0` (1 suite
passed)
- `build-support/clang-format.sh`
- `git diff --check`
### Release note
None
### Check List (For Author)
- Test
- [x] Regression test
- [x] Unit Test
- [ ] Manual test (add detailed scripts or steps below)
- [ ] No need to test or manual test. Explain why:
- [ ] This is a refactor/code format and no logic has been changed.
- [ ] Previous test can cover this change.
- [ ] No code files have been changed.
- [ ] Other reason
- Behavior changed:
- [ ] No.
- [x] Yes. Adds an opt-in session variable for skipping file-cache
writes during TopN lazy-materialization phase 2.
- 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]
