[MXS-1134] Cache Invalidation Created: 2017-02-10 Updated: 2023-05-08 Resolved: 2019-11-06 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | cache |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.0 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Johan Wikman | Assignee: | Johan Wikman |
| Resolution: | Fixed | Votes: | 4 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Epic Link: | Cache Improvements | ||||||||||||||||||||||||
| Sprint: | MXS-SPRINT-92, MXS-SPRINT-93 | ||||||||||||||||||||||||
| Description |
|
Currently there is no cache invalidation, but for time-to-live. It would be relatively straightforward to invalidate cache entries as the result of updates, inserts and deletes. |