Skip to content

branch-4.1: [fix](outfile)Preserve DateTimeV2 scale in OUTFILE CSV. #64344 - #64714

Merged
yiguolei merged 1 commit into
branch-4.1from
auto-pick-64344-branch-4.1
Jun 23, 2026
Merged

branch-4.1: [fix](outfile)Preserve DateTimeV2 scale in OUTFILE CSV. #64344#64714
yiguolei merged 1 commit into
branch-4.1from
auto-pick-64344-branch-4.1

Conversation

@github-actions

@github-actionsgithub-actionsBot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Cherry-picked from #64344

@hubgeterYour Name
[fix](outfile)Preserve DateTimeV2 scale in OUTFILE CSV. (#64344)
a2f3e5c
CSV OUTFILE serialization for DateTimeV2 was using the value-level
default formatter, which emits six fractional digits whenever
microseconds are present. The serializer already carries the declared
DateTimeV2 scale, so pass it through and cover the local OUTFILE CSV
path with a focused Groovy regression.
example : ```
table:
CREATE TABLE test_outfile_datetimev2 (
id INT,
dt3 DATETIMEV2(3) ) ...
data :
1 2026-06-06 15:54:51.442
before outfile : 2026-06-06 15:54:51.442000
after outfile:
2026-06-06 15:54:51.442
```
@github-actions
github-actionsBot requested a review from yiguolei as a code ownerJune 23, 2026 01:56
@hello-stephen

hello-stephen commented Jun 23, 2026

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

hello-stephen commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

run buildall

@hello-stephen

hello-stephen commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

BE UT Coverage Report

Increment line coverage 100.00% (1/1) 🎉

Increment coverage report
Complete coverage report

CategoryCoverage
Function Coverage54.15% (20627/38089)
Line Coverage37.70% (196333/520720)
Region Coverage34.06% (153448/450566)
Branch Coverage35.01% (66946/191234)

@hello-stephen

hello-stephen commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 100.00% (1/1) 🎉

Increment coverage report
Complete coverage report

CategoryCoverage
Function Coverage73.77% (27459/37221)
Line Coverage57.41% (297539/518230)
Region Coverage55.08% (249896/453673)
Branch Coverage56.48% (108178/191540)

@yiguolei
yiguolei merged commit 6ae89db into branch-4.1Jun 23, 2026
29 of 32 checks passed
@morningman
morningman deleted the auto-pick-64344-branch-4.1 branch July 8, 2026 14:10
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@yiguoleiyiguoleiyiguolei approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@hello-stephen@yiguolei@hubgeter