shuke987 opened a new pull request, #64603:
URL: https://github.com/apache/doris/pull/64603
## What problem does this PR solve?
Back-ports the **ANN index-only-scan test rework** from branch-4.0 #64525 to
branch-4.1. On 4.1 Cloud-P0 the two ann cases are muted-but-flaky because
they
assert on **profile scan-bytes equality**, which is non-deterministic.
This rework (matching 4.0) **removes the flaky Cloud-P0 cases**
(`ann_index_only_scan`, `ann_index_only_scan_distance_expr`,
`ann_index_only_scan_metric_direction` + its `.out`) and replaces the
coverage
with **deterministic `nonConcurrent` debug-point tests** that force the
index-only path via
`GetDebugPoint().enableDebugPointForAllBEs("segment_iterator._read_columns_by_index",
...)`.
Verified the debug point `segment_iterator._read_columns_by_index` already
exists on branch-4.1 (`be/src/storage/segment/segment_iterator.cpp`), and the
ANN range-search product fix (#63965) is already on 4.1, so the new tests are
runnable here. **Test-only change (no FE/BE code).**
Complements #64597 (the other Cloud-P0 deflake backports).
## Cherry-picked from branch-4.0 #64525 (with `-x` provenance)
- `[test](regression) Add debug point ANN index-only scan test (#63859)`
- `[fix](test) drop unsupported enable_condition_cache var in
ann_index_only_scan debug_point cases`
- `[fix](test) drop unsupported enable_condition_cache var in
ann_range_search cases`
## Not included (separate follow-up)
- `[fix](compaction) let time_series_level2_file_count debug point bypass …`
— touches BE
(`cumulative_compaction_time_series_policy.cpp`, which moved to
`be/src/storage/compaction/`
on 4.1 due to the BE dir refactor #61595), so it needs a manual port + a
remote compile
verification before submitting; handled separately.
## Release note
None
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
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]
