-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Filtering by user_id in graph memory search results does not work #1805
Comments
Hi @nibankougen we knew about this issue and released a patch last week. Could you please upgrade your mem0 package? Let me know if you are still having this problem. |
There is another problem with graph memory sometimes not registering, but the filtering by
|
by viewing the source code, class MemoryGraph:
def __init__(self, config):
self.config = config
self.graph = Neo4jGraph(self.config.graph_store.config.url, self.config.graph_store.config.username, self.config.graph_store.config.password)
self.embedding_model = EmbedderFactory.create(
self.config.embedder.provider, self.config.embedder.config
)
if self.config.llm.provider:
llm_provider = self.config.llm.provider
if self.config.graph_store.llm:
llm_provider = self.config.graph_store.llm.provider
else:
llm_provider = "openai_structured"
self.llm = LlmFactory.create(llm_provider, self.config.llm.config)
self.user_id = None
self.threshold = 0.7 You can see self.user_id = None |
@chenm1xuexi I understand your concern. However, the user_id in the add call is used to create the source node. Why do you think resetting "user_id" matters for search? |
🐛 Describe the bug
The vector memory search result (
memories
) is filtered byuser_id
, but the graph memory search result (entities
) is not filtered byuser_id
, is this correct behavior? I expected graph memory search results to be filtered byuser_id
as well as vector memory ones.For example, I executed the following code using vector memory and graph memory.
The execution result is as follows.
Here are the results I expect.
The text was updated successfully, but these errors were encountered: