Mryange opened a new pull request, #68828:
URL: https://github.com/apache/doris/pull/68828
[fix](be) Report TIME column metadata correctly
### What problem does this PR solve?
Issue Number: N/A
Problem Summary: Views containing TIME expressions report `unknown` for both
`DATA_TYPE` and `COLUMN_TYPE` in `information_schema.columns`, preventing
clients from identifying the type. Root cause: the BE schema scanner does not
handle TIMEV2 in its type-name mappings or temporal precision rules. Return
`time` / `time(n)`, populate `DATETIME_PRECISION`, and leave numeric precision
fields NULL, following DATETIMEV2 behavior.
### Release note
Fix TIME column type names and precision metadata in
`information_schema.columns`.
### Check List (For Author)
- Test
- [ ] Regression test
- [x] Unit Test
- `bash run-be-ut.sh -j48 --run
--filter='SchemaColumnsScannerTest.*'` passed under ASAN (1 test). Covers
missing scale, scales 0/3/6, and DATETIME/DECIMAL controls. Tested before
moving the unchanged patch to the latest master base.
- [ ] Manual test
- [ ] No need to test or manual test
- Behavior changed:
- [ ] No.
- [x] Yes. Correct TIME metadata; runtime values are unchanged.
- Does this need documentation?
- [x] No.
- [ ] Yes.
### Check List (For Reviewer who merge this PR)
- [ ] Confirm the release note
- [ ] Confirm test cases
- [ ] Confirm document
- [ ] Add branch pick label
--
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]
