Hello Qdrant team!
We have a philosophical question about Qdrant. We are planning to store 1B objects in a qdrant collection, with vectors and a small payload comprised of our objects' labels as we already discussed. The use-case is of course to do similarity search between the objects and constraint this search using the labels.
But we would also like to have a reference database for our objects, to query them (without similarity search), and have more contextual data attached (creation dates, user ids, nested data and lot more).
We were wondering if you think Qdrant could be suitable as a database + a vector search engine, and is this a use-case for which you will build features in the future (more payload types, filtering performance optimizations...). Or would you advice to use a secondary database and focus on using Qdrant as a vector search engine in sync with a primary storage?