[Bug]: Properties of relationships not saved in graph when adding a document - Postgres
Do you need to file an issue?
- [x] I have searched the existing issues and this bug is not already filed.
- [x] I believe this is a legitimate bug, not just a question or feature request.
Describe the bug
- Uploading a document in the postgres graph storage results with the column "properties" of DIRECTED table empty for all rows.
- This causes a failure in the retrieval step for the global query mode, as no relationship's property is found in the database
Steps to reproduce
- Upload a document in postgres storage (first document of the db/graph)
- Launch query with mode: global
- No relations found
- Answer says that there was no relevant context
Expected Behavior
- Populate the "property" column of the DIRECTED table with the properties of each relationship
- Retrieve the relationships relevant to the query in the global query mode, creating the relevant context for the generation of the answer
LightRAG Config Used
- LightRag version 1.2.1
Logs and screenshots
INFO:Logger initialized for working directory: ./data **** Start Global Query **** INFO:Non-embedding cached missed(mode:global type:query) INFO:Non-embedding cached missed(mode:global type:keywords) INFO:Inserting 1 to llm_response_cache INFO:Query edges: Entità finanziarie, DORA, Regolamentazione finanziaria, top_k: 60, cosine: 0.2 WARNING:No valid text chunks found INFO:Global query uses 0 entites, 0 relations, 0 chunks INFO:Inserting 1 to llm_response_cache Non ho informazioni specifiche riguardo al DORA e le entità finanziarie a cui si applica. Ti consiglio di consultare fonti ufficiali o documentazione specifica per ottenere dettagli accurati su questo argomento. Global Query Time: 8.701498031616211
Additional Information
- LightRAG Version: 1.2.1
- Operating System: Windows
- Python Version: 3.11.9
- Related Issues: NA
have you configure age extension to save graph info ?
have you configure age extension to save graph info ?
You mean installing the extension, creating the indexes and making sure that the objects are there? Yes.
UPD: The properties are missing only wrt relationships, in nodes they are saved just fine to Postgres.
Im having this same issue with a postgres image I built with the extensions pre-installed.
but when I use the shangor/postgres-for-rag:v1.0 image recommended in the docs, It works fine. I'm not sure what can be happening.
Hello @fedehann, I have exactly the same problem you described.
Have you managed to resolve it in any other way?
@fedehann I found the same issue in 1.3.3 with Azure postgres. Did you figure out the solution?