[MCOL-5480] LDI loads values incorrectly for MEDIUMINT, TIME and TIMESTAMP when cpimport is used for batch insert Created: 2023-04-20 Updated: 2023-09-20 Resolved: 2023-05-30 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | DMLProc |
| Affects Version/s: | None |
| Fix Version/s: | 23.02.4 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Daniel Lee (Inactive) | Assignee: | Gagan Goel (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Assigned for Review: | |
||||||||
| Assigned for Testing: | |
||||||||
| Description |
|
Build tested: 23.02.02 and drone build #7534 for develop branch The issue happens only when running "load data infile" and with "set columnstore_use_import_for_batchinsert = on;". INSERT, UPDATE, as well as stand alone cpimport do not have this issue.
|
| Comments |
| Comment by Daniel Lee (Inactive) [ 2023-04-20 ] |
|
Data type TIME also has this issue Value '11:58:28" would be loaded as "838:59:59". |
| Comment by Gagan Goel (Inactive) [ 2023-05-23 ] |
|
For QA: This issue is caused by a bug in the processing of MEDIUMINT datatype in the plugin code. So if the LDI is performed on a signed/unsigned MEDIUMINT datatype along with other datatypes in the LDI, the other columns also get impacted. In testing, if you just use TIMESTAMP or TIME datatypes or both, the LDI works fine. I have added test cases to MTR that test various combinations of LDI that include load of signed/unsigned MEDIUMINT datatypes in isolation as well as with other datatypes. |
| Comment by Daniel Lee (Inactive) [ 2023-05-30 ] |
|
Build verified: develop branch engine: d083650f759152db639cab52cab530f06d7e36d9 Verified the test case above as well as MTR test case "mysql-test/columnstore/bugfixes/mcol-5480.test". |