Does namespace have a specific purpose?

[prestonvasquez]

I'm noticing that most vectorstore instrumentations (with the exception of qdrant) use Store as a wrapper for a client and typically use namespace as a collection analogue.

For MongoDB, it makes sense to have a Store object wrap a mongo.Collection since adding and searching vectors is collection-specific. In this case AddDocuments() and SimilaritySearch() become analogues for Collection.InsertMany() and Collection.Aggregate(). This also keeps our implementation inline with PY and TS. Notably, a collection / namespace isn't actually optional and makes the API awkward:

store, _ := mongovector.New(client)
if _, err := store.AddDocuments(ctx, docs); err != nil {
	panic(err) // This always errors since a collection / namespace has not been defined.
}

TL;DR: Is the Namespace option generic enough to use as an index name, or does this field have a specific but undocumented use case?

For exampe:

docs, _ := store.SimilaritySearch(ctx, "text", 20, vectorstore.WithNameSpace("some_index_to_search"))

[prestonvasquez]

CC: @blink1073 @matthewdale @qingyang-hu

[jtazin]

hi @FluffyKebab! looks like you added the namespace option, do you have any insight into @prestonvasquez's question?

[prestonvasquez]

We've decided to use the namespace option as a way for users to switch indexes at the operation leve.