Skip to content
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.

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

excutor: fix the date precision of builtinCastDurationAsStringSig.vecEvalString #23314 #23286 #23332

Merged
merged 6 commits into from
Mar 18, 2021

Conversation

Howie59
Copy link
Contributor

@Howie59 Howie59 commented Mar 16, 2021

What problem does this PR solve?

Issue Number: close #23314 #23286

Problem Summary:

What is changed and how it works?

Proposal: xxx

What's Changed:

How it Works:

Related changes

Check List

Tests

  • Unit test
  • Integration test
  • Manual test (add detailed scripts or steps below)
  • No code

Side effects

  • Performance regression
    • Consumes more CPU
    • Consumes more MEM
  • Breaking backward compatibility

Release note

  • fix date precision

@Howie59 Howie59 requested a review from a team as a code owner March 16, 2021 05:25
@Howie59 Howie59 requested review from XuHuaiyu and removed request for a team March 16, 2021 05:25
@ti-chi-bot ti-chi-bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Mar 16, 2021
@ti-srebot
Copy link
Contributor

@Howie59
Copy link
Contributor Author

Howie59 commented Mar 16, 2021

/rebuild

@mmyj
Copy link
Member

mmyj commented Mar 16, 2021

LGTM

@ti-chi-bot
Copy link
Member

@mmyj: Please use /LGTM instead of LGTM when you want to approve the pull request by comment.
If you use the GitHub review feature, please approve the PR directly, the comment will not take effect in the GitHub review feature.
If you have any qustions please refer to lgtm command help or lgtm plugin design.

If you have approved this PR, please ignore this reply. This reply is being used as a temporary reply during the migration of the new bot and will be removed on April 1.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

@mmyj
Copy link
Member

mmyj commented Mar 16, 2021

/LGTM

@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Mar 16, 2021
@mmyj
Copy link
Member

mmyj commented Mar 16, 2021

#23286 had been fixed also.

@Howie59 Howie59 changed the title excutor: fix date precision #23314 excutor: fix the date precision of builtinCastDurationAsStringSig.vecEvalString #23314 #23286 Mar 16, 2021
@ichn-hu ichn-hu mentioned this pull request Mar 16, 2021
@Howie59
Copy link
Contributor Author

Howie59 commented Mar 16, 2021

@XuHuaiyu PTAL

@ti-chi-bot ti-chi-bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 18, 2021
@ti-chi-bot ti-chi-bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 18, 2021
@ti-chi-bot
Copy link
Member

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • lzmhhh123
  • mmyj

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by writing /lgtm in a comment.
Reviewer can cancel approval by writing /lgtm cancel in a comment.

@ti-chi-bot ti-chi-bot added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Mar 18, 2021
@lzmhhh123 lzmhhh123 linked an issue Mar 18, 2021 that may be closed by this pull request
@lzmhhh123
Copy link
Contributor

/merge

@ti-chi-bot
Copy link
Member

This pull request has been accepted and is ready to merge.

Commit hash: 9c641f7

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Mar 18, 2021
@ti-chi-bot ti-chi-bot merged commit 6e00871 into pingcap:master Mar 18, 2021
@Howie59 Howie59 deleted the issue-23314 branch March 18, 2021 10:04
@wzru
Copy link
Contributor

wzru commented Aug 6, 2021

/label needs-cherry-pick-4.0

@wzru
Copy link
Contributor

wzru commented Aug 6, 2021

/label needs-cherry-pick-5.0

@ti-srebot
Copy link
Contributor

cherry pick to release-4.0 in PR #26970

@ti-srebot
Copy link
Contributor

cherry pick to release-5.0 in PR #26971

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/expression needs-cherry-pick-release-5.0 sig/execution SIG execution size/S Denotes a PR that changes 10-29 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

The result of GROUP_CONCAT(time) is incorrect concat time data type lost the time fsp
6 participants