Skip to content

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

Open
github-actions[bot] wants to merge 1 commit into
branch-4.0from
auto-pick-64344-branch-4.0
Open

branch-4.0: [fix](outfile)Preserve DateTimeV2 scale in OUTFILE CSV. #64344#64713
github-actions[bot] wants to merge 1 commit into
branch-4.0from
auto-pick-64344-branch-4.0

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Cherry-picked from #64344

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-actions Bot requested a review from morningman as a code owner June 23, 2026 01:55
@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

@hello-stephen

Copy link
Copy Markdown
Contributor

BE UT Coverage Report

Increment line coverage 100.00% (1/1) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 53.33% (19458/36483)
Line Coverage 36.45% (181865/498930)
Region Coverage 33.05% (141340/427594)
Branch Coverage 33.91% (61153/180360)

@hello-stephen

Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 100.00% (1/1) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 71.55% (25554/35714)
Line Coverage 54.42% (271022/498056)
Region Coverage 52.02% (224671/431912)
Branch Coverage 53.44% (96725/180993)

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.

2 participants