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

Question: Can we specify custom vector databases at kg index creation? #252

Open
rasharab opened this issue Jan 20, 2025 · 1 comment
Open

Comments

@rasharab
Copy link

rasharab commented Jan 20, 2025

You've provided custom vector retrievers, but trying to ascertain if it is currently possibly to use pinecone (for example) during KG index creation (i.e. embedding relationships etc.)

I'm assuming you guys are storing entity relationship embeddings etc. in your library using neo4j vectorstore?

Also, there's a lot of functions under indexes.py (upsert_vector_on_relationship ...) that I'm not entirely sure if they're even being used in this package.

Thank you again.

@stellasia
Copy link
Contributor

Hi @rasharab ,

You're right in assuming that the current implementation of the KG creation pipeline writes all results (nodes, relationships and embeddings) to Neo4j. If you want to change this behavior, you can create a custom KGWriter.

Regarding the functions in indexes.py, they are helper functions not used directly by other components of the package, but that users can call if they can't write Cypher queries.

Hope that helps!

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