OIiveirra opened a new pull request, #68458:
URL: https://github.com/apache/doris/pull/68458
### What problem does this PR solve?
Issue Number: DORIS-29050
Related PR: None
Problem Summary: When a Paimon table evolves a Decimal column from
DECIMAL(5,2) to DECIMAL(6,3), the forced JNI scanner used the destination Doris
precision and scale to decode the stored unscaled value. As a result, an old
value such as 1.20 could be returned as 0.120. The scanner now uses the Paimon
DecimalType precision and scale that describe the physical record, while the
existing tests verify both an evolved old value (1.20) and a current-schema
value (1.234).
### Release note
Fix incorrect Decimal values when reading Paimon files after Decimal scale
schema evolution with the forced JNI scanner.
### Check List (For Author)
- Test
- [x] Unit Test: `PaimonColumnValueTest`
- [x] Regression test: targeted Paimon Decimal scale evolution case was
validated in the personal environment; the case is not included because the
shared Spark/Paimon fixture cannot provide stable table metadata across runs.
- [ ] Manual test
- [ ] No need to test or manual test.
- Behavior changed:
- [x] Yes. Existing Paimon Decimal values are decoded with their
physical schema scale.
- [ ] No.
- 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]
