Find answers from the community

Updated 3 months ago

I'm looking at subclassing [

I'm looking at subclassing WeaviateVectorStore to use weaviate's ability to have vectors on multiple properties. Then just create multiple "WeaviateVectorStore" objects, each with a "text_key" for a specific property (eg: title, actual_text, questions, etc), to only use that property's embedding, but have it all stored in a single weaviate object.

I think a majority of it can be solved by just tweaking the WeaviateVectorStore query(),add(), etc..basically just serializing slightly differently, but I wanted to check and see if anybody had thoughts on better ways, or if thats already possible somehow and I missed it?
L
R
2 comments
That sounds like the most straightforward to me!
Perfect, thanks! I decided to dive deeper into weaviate first then wrap back around to this and hopefully make a PR for whatever it turns into.

Hopefully I'll have a better grasp of llamaindex by then too. I'm missing some key paradigm for tools like this and langchain. So instead of just grok'ing the concepts and being able to assume most of what any object does, I keep having to go to the code. C'est la vie though..still well worth it!
Add a reply
Sign up and join the conversation on Discord