Skip to content

branch-3.0: [fix](nereids) fix parse date time exception #50810 #50889

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
dataroaring merged 1 commit into from
May 14, 2025
Merged

branch-3.0: [fix](nereids) fix parse date time exception #50810 #50889

dataroaring merged 1 commit into from
May 14, 2025

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented May 14, 2025

Cherry-picked from #50810

@yujun777
[fix](nereids) fix parse date time exception (#50810)
3c6ebc2 
### What problem does this PR solve?

before this pr:

```
MySQL root@127.0.0.1:(none)> select date '2025年1月20日';
(1105, 'errCode = 2, detailMessage = date/datetime literal [2025年1月20日] is invalid')
```

after this pr:

```
MySQL root@127.0.0.1:(none)> select date '2025年1月20日';
+----------------------+
| date '2025年1月20日' |
+----------------------+
| 2025-01-20           |
+----------------------+
```
@github-actions github-actions bot requested a review from dataroaring as a code owner May 14, 2025 07:18
@hello-stephen
Copy link
Contributor

hello-stephen commented May 14, 2025

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?

@dataroaring dataroaring reopened this May 14, 2025
@hello-stephen
Copy link
Contributor

hello-stephen commented May 14, 2025

run buildall

dataroaring
dataroaring approved these changes May 14, 2025
View reviewed changes
Copy link
Contributor

@dataroaring dataroaring left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@dataroaring dataroaring merged commit 8dbde04 into branch-3.0 May 14, 2025
22 of 24 checks passed
@github-actions github-actions bot deleted the auto-pick-50810-branch-3.0 branch May 14, 2025 13:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@dataroaring dataroaring dataroaring 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.

4 participants

@hello-stephen @dataroaring @yujun777