Andrey Vasnetsov

> What is the rationale for not allowing users to rename a collection? I cannot think of a DBMS that would not allow users to rename tables / databases. This...

> Note that if you really want to change your collection name, what you can do is this: This will only work for single-node cluster, and overall not recommended

> we need access to the individual scores from each prefetch, not just the final fused score. You can simply use batch search for that

You need to have all collections with replication factor of at least 2 to achieve that

You should not restart pods all at once, use rolling restart instead. If you need more help with DevOps around qdrant, I would recommend to go for our hybrid cloud.

no, changes in helm won't be reflected in existing collections

Missing support for creating sparse and multi-vectors

Might be a related discussion here: https://discord.com/channels/907569970500743200/1335658066104029305

@viktorku can you please share logs of the qdrant process at the start? It should have FS check running there. (Only available in 1.15.x)

https://github.com/qdrant/qdrant/issues/3628