Find answers from the community

Updated 3 months ago

Weaviate

If im using propertygraphindex with neo4j and weaviage and i want to store the node embeddings in both but only caclaute then in weaviate (using t2vectransf), how do i setup the embedding pipeline. Should i add to the weaviate index then retrieve embeddings from weaviage then add them to the nodes for the propertygraphindex with ember nodes as false?
L
t
8 comments
Hmmm, I think that sounds right.

Just curious, but why do you want to use weaviates embedding pipeline vs embedding yourself?
The way things are embedded into weaviate is a little specific though
Basically it's a text node, where the ID maps to the ID of the kg node

(Although this is an issue for some vector dbs, I just opened a pr to fix this)
Thanks. On the question, id probably invert it, why wouldnt we do that? We’ve been using weaviate in production with collections using a default embedding module for a while now and it works well (faster and more reliable than a 3rd party api) but want to move to a knowledge graph based approach and loving your new index. Slowly learning that llama index doesn’t love weaviate’s modules
Thanks for the fix pr too!
Yea in general, llamaindex calculates embeddings and inserts those embeddings into the vector store, rather than letting the vector store embed it 👀 (that way you can use nearly any embedding model, openai, huggingface, cohere, etc.)
Definitely! Will have a release out later today with this and a few other graph fixes
Add a reply
Sign up and join the conversation on Discord