Remove zoekt legacy cache key
What does this MR do and why?
This MR removes the legacy cache key which was added to not expire all keys at once by changing the key. It was merged last milestone so it can be removed this milestone
generated by duo
Related to #517756 (closed)
This change simplifies and streamlines the caching mechanism for Zoekt search results. The main updates include:
- Removal of the legacy cache key method and its associated fingerprint generation.
- Simplification of the cache reading process by only using the current cache key, eliminating the need to check for legacy keys.
These changes likely aim to clean up old code and improve the efficiency of the caching system. By removing legacy support, the code becomes more straightforward and easier to maintain. The update also suggests that the system has moved past a transition period where backward compatibility with older cache keys was necessary.
References
Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
N/A
How to set up and validate locally
See original MR for testing instructions