I'm working on a project where I am using LangChain's RedisSemanticCache to speed up response times for repetitive queries by caching results. I am using OpenAI embeddings to create vector representations of questions and set up the cache using Redis. The problem I'm encountering is that semantically similar questions, like "What is the capital of France?" and "Can you tell me the capital city of France?", are being treated as different cache entries because they generate different embeddings.

Here’s how I’m currently setting up the cache:

semantic_cache = RedisSemanticCache(
    redis_url=REDIS_URL,
    embeddings=embeddings,
    distance_threshold=0.3,
    ttl=REDIS_TTL,
    prefix=hashlib.sha256(question.encode('utf-8')).hexdigest(),
    name=hashlib.sha256(question.encode('utf-8')).hexdigest(),
)

The issue arises because when I use hashlib.sha256() on the question string, each query generates a different cache key, even though the meaning is the same. This leads to cache misses for semantically similar queries and poor performance.

What I want to achieve: I want to ensure that semantically similar queries are stored and retrieved using the same cache key, which would allow the cache to be more effective. My goal is to avoid cache overwrites and speed up response times for similar questions without needing to re-run embeddings or queries.

However, when I try to use a static cache key (e.g., always using the same cache key), I face another problem: If I keep the cache key static, it always returns the same response from the first question, even if I ask a completely unrelated question. This prevents the system from generating answers for new queries.

Questions:

How can I ensure that semantically similar queries (with different wording) generate the same cache key? Should I preprocess the queries before hashing them to generate a standardized cache key? Is there a way to append different answers to the same key in Redis without overwriting previous ones? What is the best way to handle different variations of the same query without missing cache hits? How can I avoid the issue of always getting the first answer when using a static key for unrelated queries?