Skip to content
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

Make the graph database a configuration option #6

Open
dmccrearytg opened this issue Sep 3, 2024 · 1 comment
Open

Make the graph database a configuration option #6

dmccrearytg opened this issue Sep 3, 2024 · 1 comment

Comments

@dmccrearytg
Copy link

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.

@WuJunde
Copy link
Contributor

WuJunde commented Sep 5, 2024

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants