Gabriel39 opened a new pull request, #67904:
URL: https://github.com/apache/doris/pull/67904
### What problem does this PR solve?
Issue Number: DORIS-28910, DORIS-28911, DORIS-28912
Problem Summary:
- Paimon TIMESTAMP WITHOUT TIME ZONE predicates lost sub-millisecond
precision during conversion, which could incorrectly prune matching data files.
- A latest statement snapshot or reader-only OPTIONS alias pinned data
visibility by copying the table with time-travel options, which could roll the
bound schema back after a schema-only ALTER.
- Branch reads bound the schema from the latest data snapshot even though a
branch schema can advance without creating a data snapshot.
This change preserves the full local timestamp value, applies
statement-fence scan options without schema time travel, and uses the branch's
current schema while retaining its latest data snapshot fence.
### Release note
None
### Check List (For Author)
- Test
- [ ] 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. Paimon reads now retain microsecond predicate precision and
the current schema for latest statement and branch reads.
- 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]
