[MCOL-99] EXTRACT() function returns an exception when processing *MICROSECONDS Created: 2016-06-02  Updated: 2016-10-05  Resolved: 2016-10-05

Status: Closed
Project: MariaDB ColumnStore
Component/s: ExeMgr
Affects Version/s: None
Fix Version/s: 1.0.4

Type: Bug Priority: Major
Reporter: Daniel Lee (Inactive) Assignee: Daniel Lee (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
PartOf
is part of MCOL-280 Beta issues Closed
Sprint: 2016-19

 Description   

Build tested:

mscadmin> getsoft
getsoftwareinfo Thu Jun 2 09:55:23 2016

Name : mariadb-columnstore-platform Relocations: (not relocatable)
Version : 1.0 Vendor: MariaDB Corporation Ab
Release : 0 Build Date: Fri 27 May 2016 03:07:53 PM CDT
Install Date: Mon 30 May 2016 10:07:40 AM CDT Build Host: srvbuilder
Group : Applications Source RPM: mariadb-columnstore-1.0-0.src.rpm

The issue was reported by autopilot's distributed function test case

The following queries have the *MICROSECOND issue:

11 select cidx, CDATE, EXTRACT(MINUTE_MICROSECOND FROM CDATE) from datatypetestm order by cidx;
13 select cidx, CDATE, EXTRACT(HOUR_MICROSECOND FROM CDATE) from datatypetestm order by cidx;
16 select cidx, CDATE, EXTRACT(DAY_MICROSECOND FROM CDATE) from datatypetestm order by cidx;
33 select cidx, CDATETIME, EXTRACT(HOUR_MICROSECOND FROM CDATETIME) from datatypetestm order by cidx;
53 select cidx, CDATE from datatypetestm where EXTRACT(HOUR_MICROSECOND FROM CDATE) <> CDATE order by cidx;
56 select cidx, CDATE from datatypetestm where EXTRACT(DAY_MICROSECOND FROM CDATE) <> CDATE order by cidx;
73 select cidx, CDATETIME from datatypetestm where EXTRACT(HOUR_MICROSECOND FROM CDATETIME) <> CDATETIME order by cidx;
76 select cidx, CDATETIME from datatypetestm where EXTRACT(DAY_MICROSECOND FROM CDATETIME) <> CDATETIME order by cidx;

Errors returned:

[root@columnStore CNX]# cat EXTRACT.DM.sql.diff.log| grep -i error
> ERROR 1815 (HY000) at line 11: Internal error: st: 0 TupleBPS::receiveMultiPrimitiveMessages() caught an exception: IDB-2035: An internal error occurred. Check the error log file & contact support.
> ERROR 1815 (HY000) at line 13: Internal error: st: 0 TupleBPS::receiveMultiPrimitiveMessages() caught an exception: IDB-2035: An internal error occurred. Check the error log file & contact support.
> cidERROR 1815 (HY000) at line 16: Internal error: st: 0 TupleBPS::receiveMultiPrimitiveMessages() caught an exception: IDB-2035: An internal error occurred. Check the error log file & contact support.
> select cidx, CDATETIME,ERROR 1815 (HY000) at line 31: Internal error: st: 0 TupleBPS::receiveMultiPrimitiveMessages() caught an exception: IDB-2035: An internal error occurred. Check the error log file & contact support.
> ERROR 1815 (HY000) at line 33: Internal error: st: 0 TupleBPS::receiveMultiPrimitiveMessages() caught an exception: IDB-2035: An internal error occurred. Check the error log file & contact support.
> select cidx, CDATETIME, EXTRACT(HOUR_MINUTE FROM CDATETIME) from datatypetestm orderERROR 1815 (HY000) at line 36: Internal error: st: 0 TupleBPS::receiveMultiPrimitiveMessages() caught an exception: IDB-2035: An internal error occurred. Check the error log file & contact support.
> select cidx, CDATE from datatypetestm where EXTRACT(WEEK FROM CDATE) <>ERROR 1815 (HY000) at line 51: Internal error: st: 0 TupleBPS::receiveMultiPrimitiveMessages() caught an exception: IDB-2035: An internal error occurred. Check the error log file & contact support.
> ERROR 1815 (HY000) at line 53: Internal error: st: 0 TupleBPS::receiveMultiPrimitiveMessages() caught an exception: IDB-2035: An internal error occurred. Check the error log file & contact support.
> ERROR 1815 (HY000) at line 56: Internal error: st: 0 TupleBPS::receiveMultiPrimitiveMessages() caught an exception: IDB-2035: An internal error occurred. Check the error log file & contact support.
> --------ERROR 1815 (HY000) at line 71: Internal error: st: 0 TupleBPS::receiveMultiPrimitiveMessages() caught an exception: IDB-2035: An internal error occurred. Check the error log file & contact support.
> ERROR 1815 (HY000) at line 73: Internal error: st: 0 TupleBPS::receiveMultiPrimitiveMessages() caught an exception: IDB-2035: An internal error occurred. Check the error log file & contact support.
> ERROR 1815 (HY000) at line 76: Internal error: st: 0 TupleBPS::receiveMultiPrimitiveMessages() caught an exception: IDB-2035: An internal error occurred. Check the error log file & contact support.



 Comments   
Comment by David Hall (Inactive) [ 2016-09-26 ]

This bug is related to MCOL-80 and was fixed at the same time. The final fix was inserted with the merge with server 10.1.17.

Comment by Daniel Lee (Inactive) [ 2016-10-05 ]

Build verified: 1.0.4-1

mcsadmin> getsoft
getsoftwareinfo Tue Oct 4 22:29:41 2016

Name : mariadb-columnstore-platform
Version : 1.0.4
Release : 1
Architecture: x86_64
Install Date: Tue 04 Oct 2016 01:38:36 PM CDT
Group : Applications/Databases
Size : 11506458
License : Copyright (c) 2016 MariaDB Corporation Ab., all rights reserved; redistributable under the terms of the GPL, see the file COPYING for details.
Signature : (none)
Source RPM : mariadb-columnstore-platform-1.0.4-1.src.rpm
Build Date : Fri 30 Sep 2016 01:02:40 PM CDT

MariaDB [mytest]>
MariaDB [mytest]> select cidx, CDATETIME from datatypetestm where EXTRACT(DAY_MICROSECOND FROM CDATETIME) <> CDATETIME order by cidx;
-------------------------+

cidx CDATETIME

-------------------------+

1 1997-01-01 00:00:00
2 1997-01-01 00:00:01
3 1997-01-02 00:00:01
4 1997-01-03 00:00:02
5 1997-01-04 00:00:03
6 2009-12-31 23:59:56
7 2009-12-31 23:59:57
8 2009-12-31 23:59:58
9 2009-12-31 23:59:59
10 2009-12-31 23:59:59
11 2009-12-31 23:59:59

-------------------------+
11 rows in set (0.41 sec)

MariaDB [mytest]> select cidx, CDATE, EXTRACT(MINUTE_MICROSECOND FROM CDATE) from datatypetestm order by cidx;
------------------------------------------------------

cidx CDATE EXTRACT(MINUTE_MICROSECOND FROM CDATE)

------------------------------------------------------

1 1997-01-01 0
2 1997-01-01 0
3 1997-01-02 0
4 1997-01-03 0
5 1997-01-04 0
6 2009-12-28 0
7 2009-12-29 0
8 2009-12-30 0
9 2009-12-31 0
10 2009-12-31 0
11 2009-12-31 0

------------------------------------------------------
11 rows in set (0.34 sec)

Generated at Thu Feb 08 02:18:30 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.