[MCOL-4278] Select count(*) may leave table in a bad state Created: 2020-08-26 Updated: 2020-10-05 Resolved: 2020-09-25 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | MDB Plugin |
| Affects Version/s: | 1.4, 1.5.3 |
| Fix Version/s: | 5.4.1 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | David Hall (Inactive) | Assignee: | Daniel Lee (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||
| Description |
|
If @@sql_select_limit is set, followed by a select count This behavior is intermittent, meaning it may or may not happen on any given attempt. 2147483647 is max int32_t.
########################################
Do not restart mariadb-columnstore.
|
| Comments |
| Comment by Roman [ 2020-09-02 ] |
|
I haven't seen this issue in U18. I'll check centos. |
| Comment by Daniel Lee (Inactive) [ 2020-09-22 ] |
|
Build tested: 1.5.4-1 ( Drone #689) Reproduced the issue at first attempt. My environment is a Vagrant virtual machine. |
| Comment by Roman [ 2020-09-24 ] |
|
The issue had been caused by the code in rnd_end() in the plugin. The code quits early when sql_select_limit is set so that smart pointer to cpsm_tplsch_t hangs in the air and is used for the next query. cpsm_tplsch_t contains Column types so that forces fetchNextRow to use an incorrect accessor retrieving the column value, e.g. getUintvalue<8>() for an INT column. |
| Comment by Roman [ 2020-09-24 ] |
|
Plz review. |
| Comment by Daniel Lee (Inactive) [ 2020-09-25 ] |
|
Build verified: 5.4.1 (Drone #759) |