[MCOL-4096] On DEB distributions LDI returns a value saturation error when using cpimport insert insert Created: 2020-06-24 Updated: 2020-11-10 Resolved: 2020-11-10 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | DMLProc |
| Affects Version/s: | 1.5.2 |
| Fix Version/s: | 5.5.1 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Daniel Lee (Inactive) | Assignee: | Daniel Lee (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Build tested: 1.5.2-1 (community edition, hasty b33685) Distributions tested: Debian 9.1 and 10, Ubuntu 16.04, 18.04, and 20.04. When running "load data infield" with columnstore_use_import_for_batchinsert=1, LDI returned a value saturation error: MariaDB [mytest]> load data infile "/data/qa/source/dbt3/1g/orders.tbl" into table orders fields terminated by "|"; But all rows were actually loaded. LDI without using batch insert, as well as cpimport itself, did not complain about value saturation. 1.5.2-1 on Centos 7, 8, Suse 12, 15 did not have this issue. |
| Comments |
| Comment by David Hall (Inactive) [ 2020-11-09 ] |
|
Please retest withe 5.5 |
| Comment by Daniel Lee (Inactive) [ 2020-11-10 ] |
|
Build verified: 5.4.3-1 It is no longer an issue. Tested with columnstore_use_import_for_batchinsert set to ON, OFF, ALWAYS. |