I started getting into Weaviate vector store and it seems like it has many more options for inserting documents and performing queries than what the GPT-Index wrapper provides. Any insights on how I should work with it in combination with GPT-Index?
@Logan M In Weaviate you can create classes of objects, say a document with meta data fields such as filename, doc type, etc, and a paragraph class with its own fields and embedding vector associated. Gptindex only allows you to query the whole index, instead of only querying paragraphs with specific data or those belong to a certain document.
Maybe I can look into adding this functionality at some point. The support is nearly there in llama index, as we have keyword filtering, so why not type filtering right?
Right, different than keyword filtering, but I just meant the code mostly has the infrastructure to do this (which means it's not too hard to add) :dotsCATJAM:
That's great! Btw, also when adding new objects you can add objects belonging to different classes with their relevant fields which I think is also not supported today