Fix the incompatible behavior when handling IN(Timestamp | MysqlTime * ) expressions with timezone (#9779)#9826
Conversation
|
This cherry pick PR is for a release branch and has not yet been approved by triage owners. To merge this cherry pick:
DetailsInstructions 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 kubernetes-sigs/prow repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gengliqi, solotzg The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test pull-unit-test |
|
@solotzg: The specified target(s) for Use DetailsIn response to this:
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 kubernetes-sigs/prow repository. |
|
/test pull-unit-test |
This is an automated cherry-pick of #9779
What problem does this PR solve?
Issue Number: close #9778
Problem Summary:
DAGExpressionAnalyzerhasn't deal with timezone when handling set forIN()express.What is changed and how it works?
Check List
Tests
Side effects
Documentation
Release note