toMyDateTime from source type is not supported yet
Open
Nobody has claimed this yet.
affects-5.1
affects-6.0
affects-6.1
component/compute
severity/minor
type/bug
- Dominant language
- C++
- Stars
- 1k
- Forks
- 423
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 24
Description
Mini reproduce:
CREATE TABLE `t3` (
`c_int` int(11) DEFAULT NULL,
`c_str` varbinary(40) NOT NULL,
`c_datetime` datetime DEFAULT NULL,
`c_timestamp` timestamp NULL DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin;
insert into t3 values(5,0x616666656374696F6E61746520706F6974726173,null,"2020-03-29 15:24:13");
alter table t3 set tiflash replica 1;
(select c_int, c_str, c_timestamp from t3 ) union all (select c_int, c_str, c_timestamp from t3 ); -- expect successfully; but got
-- ERROR 1105 (HY000): other error for mpp stream: DB::Exception: toMyDateTime from source type is not supported yet
5.1 version
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the SQL example against TiFlash 5.1 and trace the MPP stream error mentioning toMyDateTime from source type is not supported yet. The work is done when the repeated UNION ALL query with the timestamp column succeeds without the conversion error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100