[MDEV-26842] ROW_NUMBER is not set and differs from the message upon WARN_DATA_TRUNCATED produced by inplace ALTER Created: 2021-10-15 Updated: 2021-10-26 Resolved: 2021-10-20 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Data Definition - Alter Table |
| Affects Version/s: | N/A |
| Fix Version/s: | 10.7.1 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Elena Stepanova | Assignee: | Rucha Deodhar |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
Note: algorithm=INPLACE is default for this ALTER, I only specify it for clarity.
If the algorithm is set to COPY (or if the table is MyISAM, then COPY is default), then ROW_NUMBER is set as expected. There are likely to be many places where inplace ALTER bypasses ROW_NUMBER initialization; the problem here is that the value ends up to be different from the error message. |
| Comments |
| Comment by Elena Stepanova [ 2021-10-15 ] |
|
Please feel free to demote/remove from 10.7 "must do" list if it's outside the scope. |
| Comment by Rucha Deodhar [ 2021-10-17 ] |
|
Patch: https://github.com/MariaDB/server/commit/9e8a961ee32ff1b86afa59a10a27797e58dbe2f0 |
| Comment by Sergei Golubchik [ 2021-10-18 ] |
|
9e8a961ee32ff1b86afa59a10a27797e58dbe2f0 is ok to push |
| Comment by Rucha Deodhar [ 2021-10-19 ] |
|
pushed to bb-10.7-row_number |