-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
session: add default_week_format to builtinGlobalVariable #21511
Conversation
/label component/session , needs-cherry-pick-3.0 , needs-cherry-pick-4.0 , sig/DDL , status/PTAL , type/bug-fix |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/merge |
Your auto merge job has been accepted, waiting for:
|
/run-all-tests |
@kennytm merge failed. |
(Race in TestClusterIndexCBOPointGet, #21620) |
/merge |
/run-all-tests |
@kennytm merge failed. |
/merge |
/run-all-tests |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-3.0 in PR #21622 |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-4.0 in PR #21623 |
What problem does this PR solve?
Issue Number: close #21510
Problem Summary:
WEEK()
did not recognize@@GLOBAL.default_week_format
until it has been explicitly read.What is changed and how it works?
What's Changed:
Add
default_week_format
to the list ofbuiltinGlobalVariable
so it is initialized when the session starts.How it Works:
Related changes
Check List
Tests
Side effects
Release note
WEEK()
call now recognize the global@@default_week_format
even when the session one is not set explicitly.