[MCOL-3777] Wrong error every second run Created: 2020-02-10 Updated: 2020-11-12 Resolved: 2020-03-30 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | ExeMgr |
| Affects Version/s: | 1.4.2 |
| Fix Version/s: | 1.4.4, 1.5.1 |
| Type: | Bug | Priority: | Major |
| Reporter: | David Hall (Inactive) | Assignee: | Daniel Lee (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Sprint: | 2020-4, 2020-5 |
| Epic/Theme: | 1.4_regressions |
| Description |
|
Consider the following: CREATE TABLE utest1 (ukey INT, c1 TINYINT UNSIGNED, c2 SMALLINT UNSIGNED, c3 INT UNSIGNED, c4 BIGINT UNSIGNED)engine=columnstore; INSERT INTO utest1 VALUES (3,54,3766,27483646,922336854775806), (4,254,65534,4294967294,1846744073709551614),(5,255,65535,4294967295,18446744073709551615),(6,1255,165535,14294967295,118446744073709551615); c1 TINYINT will be out of range, so we expect: which is what we get. But if you run the same insert again: |
| Comments |
| Comment by Gagan Goel (Inactive) [ 2020-03-05 ] |
|
The issue was tableValuesMap structure in cal_connection_info was not cleaning up values from a previously failed insert due to a range error in strict mode. We detect whether we are at the beginning of the insert, and if so, clean up any stored values in the map from a previous insert. |
| Comment by Daniel Lee (Inactive) [ 2020-03-30 ] |
|
Builds verified: 1.4.4-1 source, 1.5.0-1 BB 1.4.4-1 /root/ColumnStore/buildColumnstoreFromGithubSource/server /root/ColumnStore/buildColumnstoreFromGithubSource/server/engine Merge pull request #1117 from drrtuy/ 1.5.0-1 engine commit: MariaDB [mytest]> CREATE TABLE utest1 (ukey INT, c1 TINYINT UNSIGNED, c2 SMALLINT UNSIGNED, c3 INT UNSIGNED, c4 BIGINT UNSIGNED)engine=columnstore; MariaDB [mytest]> INSERT INTO utest1 VALUES (3,54,3766,27483646,922336854775806), (4,254,65534,4294967294,1846744073709551614),(5,255,65535,4294967295,18446744073709551615),(6,1255,165535,14294967295,118446744073709551615); |