[MXS-4706] Cache does not invalidate when a table is ALTERed, DROPed or RENAMEd Created: 2023-08-08 Updated: 2023-08-28 Resolved: 2023-08-23 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | cache |
| Affects Version/s: | 2.5, 6.4, 22.08, 23.02 |
| Fix Version/s: | 2.5.29, 6.4.10, 22.08.8, 23.02.4 |
| Type: | Bug | Priority: | Major |
| Reporter: | Johan Wikman | Assignee: | Johan Wikman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Sprint: | MXS-SPRINT-189 | ||||||||
| Description |
|
There are a number of situations where the cache does not invalidate, although it should. All cache entries targeting a table that is ALTERed, DROPed or RENAMEd should be evicted. |
| Comments |
| Comment by Johan Wikman [ 2023-08-18 ] |
|
Need to be reverted. |