PGVector logger message level

[jmtristancho]

Change the logger message level

The library is logging at error level a situation that is not an error.
We noticed this error in our logs, but from our point of view it's an expected behavior and the log level should be warning.

[dev2049]

out of curiosity, wouldn't trying to delete a collection that's not there indicate a mistake in logic somewhere?

[jmtristancho]

Could be, but it does not have to be always the case.
This class in particular has a init parameter pre_delete_collection: bool = False to delete the collection if it exists, so you can easily "clean" the embeddings of a collection (and the collection itself).
Using the param pre_delete_collection=True any operation would trigger the error in the log until the collection exists. It could be avoided checking if the collection exists, but that would imply an extra DB access and adding useless complexity to the code using this library.

[dev2049]

Could be, but it does not have to be always the case.
This class in particular has a init parameter pre_delete_collection: bool = False to delete the collection if it exists, so you can easily "clean" the embeddings of a collection (and the collection itself).
Using the param pre_delete_collection=True any operation would trigger the error in the log until the collection exists. It could be avoided checking if the collection exists, but that would imply an extra DB access and adding useless complexity to the code using this library.

thanks for explaining @jmtristancho! makes sense