You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the Feature
I found that ragas directly dumps node and relationships directly when saving the knowledge graph, and the relationships holds all the information about the relevant node, with a very large amount of redundancy, especially in the summary_embedding field. So when saving relationships, wouldn't it be better to just save the ID of the related node instead?
Also, there are some compression methods that can be used when saving embeddings. For instances, some RAG pipelines use base64 encoding to save these embeddings.
Why is the feature important for you?
Generating test sets takes a lot of time, and it is necessary to save the knowledge graphs generated in between to be able to load the knowledge graphs directly in case of an anomaly instead of starting all over again.
The text was updated successfully, but these errors were encountered:
Describe the Feature
I found that ragas directly dumps
node
andrelationships
directly when saving the knowledge graph, and therelationships
holds all the information about the relevantnode
, with a very large amount of redundancy, especially in thesummary_embedding
field. So when savingrelationships
, wouldn't it be better to just save the ID of the related node instead?Also, there are some compression methods that can be used when saving embeddings. For instances, some RAG pipelines use base64 encoding to save these embeddings.
Why is the feature important for you?
Generating test sets takes a lot of time, and it is necessary to save the knowledge graphs generated in between to be able to load the knowledge graphs directly in case of an anomaly instead of starting all over again.
The text was updated successfully, but these errors were encountered: