TIME datatype is not supported
(MCOL-392)
|
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | PrimProc |
| Affects Version/s: | None |
| Fix Version/s: | 1.2.0 |
| Type: | Sub-Task | Priority: | Critical |
| Reporter: | Daniel Lee (Inactive) | Assignee: | Daniel Lee (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Sprint: | 2018-08, 2018-09, 2018-10, 2018-11, 2018-12, 2018-13, 2018-14, 2018-15, 2018-16, 2018-17, 2018-18 |
| Description |
|
The following query causes a primproc restart select cidx, CTIME, DAYNAME(CTIME) from datatypetestm order by cidx; |
| Comments |
| Comment by Daniel Lee (Inactive) [ 2018-05-18 ] |
|
MONTHNAME() also has the same issue select cidx, CTIME, MONTHNAME(CTIME) from datatypetestm order by cidx; |
| Comment by Andrew Hutchings (Inactive) [ 2018-06-04 ] |
|
Actually an old bug in those two functions triggered by TIME datatype. Array out of bounds problem. |
| Comment by Andrew Hutchings (Inactive) [ 2018-06-04 ] |
|
Fix pending batched with other |
| Comment by Andrew Hutchings (Inactive) [ 2018-06-07 ] |
|
Pull request in engine and regression suite to cover this. |
| Comment by Daniel Lee (Inactive) [ 2018-06-18 ] |
|
Build verified: 1.2.0-1 source /root/columnstore/mariadb-columnstore-server Merge pull request #119 from mariadb-corporation/1.1-merge-up-20180531 Merge develop-1.1 into develop /root/columnstore/mariadb-columnstore-server/mariadb-columnstore-engine Merge pull request #494 from mariadb-corporation/ |
[MCOL-1429]