feat(semantic-cache-lookup): add CacheId attribute#236
Merged
Conversation
tomkerkhove
force-pushed
the
feat/semantic-cache-lookup-cache-id
branch
from
c153137 to
2825d82
Compare
Add support for the cache-id XML attribute in the azure-openai-semantic-cache-lookup and llm-semantic-cache-lookup policies. This allows customers to target a specific named cache instance for semantic caching. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
tomkerkhove
force-pushed
the
feat/semantic-cache-lookup-cache-id
branch
from
2825d82 to
4aaa0f7
Compare
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Mielek
approved these changes
Apr 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The semantic cache lookup policies (
azure-openai-semantic-cache-lookupandllm-semantic-cache-lookup) are missing thecache-idXML attribute that the gateway supports. This attribute allows customers to target a specific named cache instance.Solution
Add
CacheIdproperty toSemanticCacheLookupConfigand update the compiler and decompiler.