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

Update README: Move Neo4J Storage Section for Better Visibility #348

Merged
merged 1 commit into from
Dec 2, 2024

Conversation

donbr
Copy link
Contributor

@donbr donbr commented Nov 29, 2024

  • The Using Neo4J for Storage section was originally nested inside the Ollama details block, making it less visible to users looking for KG storage options.
  • Moved this section to appear just before Insert Custom KG, grouping it with other Knowledge Graph-related content.
  • This change improves visibility and helps users discover Neo4J configuration details more easily.

Move `Using Neo4J for Storage` content outside of Ollama details group for improved visibility to this option.
@donbr donbr changed the title Update README: Move Neo4J Storage Section for Better Visibilit Update README: Move Neo4J Storage Section for Better Visibility Nov 29, 2024
@donbr
Copy link
Contributor Author

donbr commented Nov 29, 2024

Should we update the LightRAG init parameters table with a consistent parameter name for KG storage?

  • kg: parameter name used in neo4j code examples
  • graph_storage: parameter name shown in the table

@LarFii LarFii merged commit 0a8f524 into HKUDS:main Dec 2, 2024
1 check passed
@LarFii
Copy link
Collaborator

LarFii commented Dec 2, 2024

Yes, the parameter name has already been unified in the source code, but the demo was mistakenly not updated. I will fix it ASAP.

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

Successfully merging this pull request may close these issues.

2 participants