starocean999 opened a new pull request, #63281:
URL: https://github.com/apache/doris/pull/63281
Problem Summary:
TIMESTAMPTZ range partition bounds with explicit offsets were still
inconsistent across FE paths.
`CREATE TABLE ... PARTITION BY RANGE ... VALUES LESS THAN ('2024-01-15
13:00:00 +00:00')`
failed because the raw bound string was reparsed by `PartitionKey` and
rejected the space before the
timezone offset. This also overlaps with the existing TIMESTAMPTZ
partition-boundary handling that
must preserve explicit UTC offsets during metadata reconstruction.
This PR normalizes spaced numeric timezone offsets in the TIMESTAMPTZ
partition-key parsing path and
adds focused FE unit tests plus regression coverage for:
- direct TIMESTAMPTZ partition key parsing with explicit offsets
- CREATE TABLE with VALUES LESS THAN TIMESTAMPTZ bounds
- CREATE TABLE LIKE round-trip preservation of TIMESTAMPTZ range boundaries
None
### Check List (For Author)
- Test <!-- At least one of them must be included. -->
- [ ] Regression test
- [ ] Unit Test
- [ ] Manual test (add detailed scripts or steps below)
- [ ] No need to test or manual test. Explain why:
- [ ] This is a refactor/code format and no logic has been changed.
- [ ] Previous test can cover this change.
- [ ] No code files have been changed.
- [ ] Other reason <!-- Add your reason? -->
- Behavior changed:
- [ ] No.
- [ ] Yes. <!-- Explain the behavior change -->
- Does this need documentation?
- [ ] No.
- [ ] Yes. <!-- Add document PR link here. eg:
https://github.com/apache/doris-website/pull/1214 -->
### Check List (For Reviewer who merge this PR)
- [ ] Confirm the release note
- [ ] Confirm test cases
- [ ] Confirm document
- [ ] Add branch pick label <!-- Add branch pick label that this PR should
merge into -->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
