Skip to content

branch-4.1: [fix](be) Normalize v1 date string cast result #64575 - #64744

Merged
yiguolei merged 1 commit into
branch-4.1from
auto-pick-64575-branch-4.1
Jun 24, 2026
Merged

branch-4.1: [fix](be) Normalize v1 date string cast result #64575#64744
yiguolei merged 1 commit into
branch-4.1from
auto-pick-64575-branch-4.1

Conversation

@github-actions

@github-actionsgithub-actionsBot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Cherry-picked from #64575

@jacktengg@github-actionsYour Name
[fix](be) Normalize v1 date string cast result (#64575)
6b1b54a
Problem Summary: Strict-mode string casts to v1 DATE can return early
after parsing a compact datetime string or an hour-only time part. Those
early returns skipped the common target-type normalization, so DATE
results could keep non-zero time fields such as 2024-05-01 01:00:00
instead of 2024-05-01. Normalize the parsed value before both early
returns so DATE clears the time fields and DATETIME keeps datetime
semantics.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@github-actions
github-actionsBot requested a review from yiguolei as a code ownerJune 23, 2026 11:17
@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 Regression && UT Coverage Report

Increment line coverage 100.00% (2/2) 🎉

Increment coverage report
Complete coverage report

CategoryCoverage
Function Coverage73.68% (27425/37222)
Line Coverage57.34% (297141/518192)
Region Coverage54.97% (249373/453683)
Branch Coverage56.33% (107913/191557)

@yiguolei

yiguolei commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

skip buildall

@yiguolei
yiguolei merged commit 41be96c into branch-4.1Jun 24, 2026
32 of 34 checks passed
@morningman
morningman deleted the auto-pick-64575-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@jacktengg