Closed mfortman11 closed 3 months ago
I actually can not reproduce this error. Could you provide more details?
If you have already got a target collection in the db, recreation with same settings will not have a error. However, recreation with different settings will give you back this:
error: Error: Command "createCollection" failed with the following errors: [{"message":"The provided collection name 'collection_simple' already exists with a non-vector setting.","errorCode":"INVALID_COLLECTION_NAME"}]
I think @mfortman11 was referring to the LangChain implementation whereas this happens:
so any error server error results in "collection already exists, go ahead" which is totally wrong. But we should fix it in langchain.
Added in 39ad42e37fb14711041cc6ec905bbfa4c745944e in signature-cleanup
—will close issue when merged
Not an issue anymore in the v1.0.0 release
When implementing a
create if does not exist
type of method the logs are bogged down w/ error logs and the error is not catchable.This method should throw an appropriate error or we should have a create if does not exist method