I agree on the over hype. I think you can get most of the features you are talking about through metadata tagging in vector dbs. So at that point it becomes a question of which is more affordable/quicker and I guess we don't definitively know.
But also to your point, some vector dbs have top k similar caps so a db with records above these caps wouldn't return all records like a sql where query.
In terms of semantic search you are pretty much running the same process unless you are implement some custom distance metric which is doable in most vector dbs.
So, you are totally correct on the cargo culting thing but there could be a benefit if it is faster/cheaper or tremendous downside if it is slower/more expensive. I guess we will never know.
But functionality is the same if you choose the right vec db or a relational db
** Edit **
If I am wrong, call me an idiot and let me know where i am wrong
I agree on the over hype. I think you can get most of the features you are talking about through metadata tagging in vector dbs. So at that point it becomes a question of which is more affordable/quicker and I guess we don't definitively know.
But also to your point, some vector dbs have top k similar caps so a db with records above these caps wouldn't return all records like a sql where query.
In terms of semantic search you are pretty much running the same process unless you are implement some custom distance metric which is doable in most vector dbs.
So, you are totally correct on the cargo culting thing but there could be a benefit if it is faster/cheaper or tremendous downside if it is slower/more expensive. I guess we will never know.
But functionality is the same if you choose the right vec db or a relational db
** Edit **
If I am wrong, call me an idiot and let me know where i am wrong