Skip to content

branch-4.1: [fix](regression) Stabilize rowsets timestamp filters #65050#65954

Merged
yiguolei merged 1 commit into
branch-4.1from
auto-pick-65050-branch-4.1
Jul 24, 2026
Merged

branch-4.1: [fix](regression) Stabilize rowsets timestamp filters #65050#65954
yiguolei merged 1 commit into
branch-4.1from
auto-pick-65050-branch-4.1

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Cherry-picked from #65050

### What problem does this PR solve?

Issue Number: None

Problem Summary: The system rowsets regressions used second-level
current timestamps as lower bounds for `NEWEST_WRITE_TIMESTAMP`. In one
test, the timestamp was captured after the table was created and could
filter out the initial rowset on a boundary race. In the cloud-only scan
variant, the timestamp could be equal to the create-table rowset
timestamp and unexpectedly include version `0-1`. Capture stable lower
bounds on the intended side of table creation for each case, so the
tests still exercise timestamp filters while avoiding second-level
boundary races.

### Release note

None

### Check List (For Author)

- Test:
- Regression test: `./run-regression-test.sh --run -d query_p0/system -s
test_query_sys_rowsets`
- Regression test: `./run-regression-test.sh --run -d query_p0/system -s
test_query_sys_rowsets` (200 consecutive runs)
- Regression test: `./run-regression-test.sh --run -d query_p0/system -s
test_query_sys_scan_rowsets` (local non-cloud guard path)
- Regression test: `./run-regression-test.sh --run -d query_p0/system -s
test_query_sys_rowsets`
- Behavior changed: No
- Does this need documentation: No
@github-actions
github-actions Bot requested a review from yiguolei as a code owner July 23, 2026 07:44
@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?

@hello-stephen

Copy link
Copy Markdown
Contributor

run buildall

@yiguolei
yiguolei merged commit b58b813 into branch-4.1 Jul 24, 2026
28 of 31 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants