Skip to content

branch-4.1: [fix](user variable) Preserve TIMESTAMPTZ user variable type #66833 - #67128

Open
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-66833-branch-4.1
Open

branch-4.1: [fix](user variable) Preserve TIMESTAMPTZ user variable type #66833#67128
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-66833-branch-4.1

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Cherry-picked from #66833

TIMESTAMPTZ user variables could lose their original type when converted
from a legacy literal to a Nereids literal. The value was restored as a
string, which changed timezone rendering and comparison semantics after
the session timezone changed.

Root cause: `ConnectContext.getLiteralForUserVar` did not handle
`DateLiteral` and fell back to string conversion. This change uses the
existing legacy literal conversion path to preserve the TIMESTAMPTZ
type, scale, and instant value.
@github-actions
github-actions Bot requested a review from yiguolei as a code owner August 25, 2026 11:15
@hello-stephen

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

Copy link
Copy Markdown
Contributor

run buildall

@hello-stephen

Copy link
Copy Markdown
Contributor

FE Regression Coverage Report

Increment line coverage 100.00% (2/2) 🎉
Increment coverage report
Complete coverage report

@hello-stephen

Copy link
Copy Markdown
Contributor

FE UT Coverage Report

Increment line coverage 50.00% (1/2) 🎉
Increment coverage report
Complete coverage report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants