C-lara - Hi all, I know from previous discussio...
Hi all, I know from previous discussions that vector search is on the plate for future TypeDB developments. I currently always work with a TypeDB/Weaviate combination but as it creates synchronization overhead I would love to learn more about the intended timeline for vector search 😇
I have a client showing genuine interest in TypeDB but one of their main interests is to have vector search included in the solution (like MongoDB).
2 Replies
Hi @C-lara ! it's on our radar but not prioritized at the minute! We were watching the space to see how things are shaking out and which vector providers are still on their feet a year later... i suppose that's about this time
I'm curious how you're combining these two and synchronizing them?
Thanks for getting back to me @joshua
In the beginning I configured Weaviate collections and cross references similarly to the TypeDB schema but learned over time that it's too much overhead. Now, I dump basically only string/non literal attributes per schema type and insert into Weaviate whenever I create/update an instance and delete it when the instance gets deleted. Works actually quite nice as one can filter semantically and then nail it down through the Type system BUT big fan of one ring to rule them all 😄 so whenever vectors become a thing in TypeDB please let me know! 🙂