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
Our customers use TigerGraph, not Neo4j. This is because TigerGraph is a distributed graph, and can support queries over multiple servers. We want Med-Graph-RAG to work on existing healthcare graphs that already have billions of vertices and edges.
I want to work with this team to refactor the code so that the back-end database can be customized using some configuration file.
Please let me know your thoughts on this topic. I may not understand the code enough to understand the difficulty of this task.
The text was updated successfully, but these errors were encountered:
@dmccrearytg I’m glad to see Med-Graph-RAG can interface with various graph servers. I believe it shouldn’t be too difficult to do. Feel free to submit a pull request, and I’ll review the code.
Our customers use TigerGraph, not Neo4j. This is because TigerGraph is a distributed graph, and can support queries over multiple servers. We want Med-Graph-RAG to work on existing healthcare graphs that already have billions of vertices and edges.
I want to work with this team to refactor the code so that the back-end database can be customized using some configuration file.
Please let me know your thoughts on this topic. I may not understand the code enough to understand the difficulty of this task.
The text was updated successfully, but these errors were encountered: