Open viktorku opened 2 weeks ago
Hi @viktorku
We've indeed deprecated InitFrom
functionality, since it might not work correctly if there are ongoing write operations in the source collection
Hence the warning
Thanks for the clarification @joein. Does it make sense to have a warning that communicates that? I'm currently using it only for migrations during downtime, and no ongoing operations will obstruct the "copy" process.
If the plan is to ultimately remove the init_from functionality altogether, then I'd have to resort to calling the API directly. But it wouldn't make sense to remove it from the client if the service still supports it...
I'm creating collections using the documented example as found on the official website documentation. However I constantly get warnings that
init_from is deprecated
and I wasn't even able to find it in the repo here.I also see that
init_from
is supported on the API itself with no sign of deprecation soon.I have no issues with the newly created collections, but the deprecation warning is a bit off-putting.
I'm using
qdrant-client@1.9.1
and running the service in a container from theqdrant/qdrant:v1.9.5
image on x86_64 Linux