▸case-01 I am currently running a self-hosted Qdrant cluster on version 1.14.x and need to bring it up to version 1.17.x. Could you outline the recommended migration path, readiness checklist, and deployment considerations for this multi-version jump? | fail→pass | 27,185 | 12,889 | -53% | 1 | 1 | 0% | 3,481 | 3,316 | -5% | 0 | 0 | — |
▸case-02 We plan to upgrade our production Qdrant database and client libraries to the next minor release. What is the proper sequence of updates and system requirements to ensure high availability and prevent downtime during the process? | fail→pass | 22,373 | 8,016 | -64% | 1 | 1 | 0% | 2,919 | 2,614 | -10% | 0 | 0 | — |
▸case-03 Our team recently completed a Qdrant upgrade, but we noticed that the floating-point similarity scores returned by our queries have shifted compared to our previous baseline. How should we troubleshoot and evaluate our search results following this version change? | fail→pass | 17,398 | 7,226 | -58% | 1 | 1 | 0% | 2,746 | 2,338 | -15% | 0 | 0 | — |
▸case-04 We have a single-node self-hosted Qdrant deployment with a replication factor of 1 running version 1.15.2. We want to apply a rolling restart upgrade to 1.16.0 with zero downtime during business hours. What procedure should we follow? | fail→pass | 16,324 | 8,313 | -49% | 1 | 1 | 0% | 2,702 | 2,688 | -1% | 0 | 0 | — |
▸case-05 We manage a managed Qdrant Cloud cluster currently at version 1.15.1 and want to upgrade to version 1.17.0. On self-hosted setups, multi-version jumps require manual intermediate upgrades. Do we need to trigger manual intermediate updates on Qdrant Cloud? | fail→pass | 17,297 | 4,584 | -73% | 1 | 1 | 0% | 2,125 | 1,918 | -10% | 0 | 0 | — |
▸case-06 We are preparing to upgrade our self-hosted Qdrant database from 1.16.x to 1.17.x. If we detect regressions in our staging environment after the upgrade, can we run live data downgrades on the upgraded database, or what is the recommended rollback procedure? | pass→pass | 11,397 | 6,097 | -47% | 1 | 1 | 0% | 2,075 | 2,243 | +8% | 0 | 0 | — |
▸case-07 We just finished rolling out version 1.17.0 to node 1 of our 3-node Qdrant cluster. The monitoring dashboard shows HTTP endpoints are healthy. Is it safe to consider the cluster upgrade complete and start using new 1.17 API features immediately? | pass→pass | 11,950 | 8,541 | -29% | 1 | 1 | 0% | 1,736 | 2,364 | +36% | 0 | 0 | — |
▸case-08 We are upgrading Qdrant from 1.14.0 to 1.17.0 on self-hosted servers. When reviewing release notes prior to migration, is it sufficient to read only the release notes for version 1.17.0? | pass→pass | 10,704 | 4,887 | -54% | 1 | 1 | 0% | 1,879 | 2,091 | +11% | 0 | 0 | — |
▸case-09 We are sizing a Qdrant node for an upcoming minor version upgrade. The instance currently runs with 1 vCPU core since baseline query load is low. Should we keep 1 vCPU during the upgrade or increase CPU capacity? | pass→pass | 15,640 | 6,860 | -56% | 1 | 1 | 0% | 2,013 | 2,142 | +6% | 0 | 0 | — |
▸case-10 We upgraded our Python application's Qdrant SDK to 1.17.0, but our Qdrant server cluster is still on version 1.16.2. Will our client application encounter compatibility errors when connecting to the cluster? | pass→pass | 8,570 | 5,611 | -35% | 1 | 1 | 0% | 1,495 | 2,124 | +42% | 0 | 0 | — |
▸case-11 We want to automate version upgrades for our Qdrant Cloud clusters using a command-line utility in our CI/CD pipeline. Which CLI tool should we integrate to manage Qdrant Cloud operations? | fail→pass | 11,799 | 3,722 | -68% | 1 | 1 | 0% | 2,022 | 1,669 | -17% | 0 | 0 | — |
▸case-12 Before applying a minor version upgrade to our production Qdrant cluster, what pre-upgrade testing steps should be performed in our staging environment to catch potential client-side issues? | fail→pass | 17,914 | 10,917 | -39% | 1 | 1 | 0% | 2,432 | 2,611 | +7% | 0 | 0 | — |
▸case-13 After upgrading Qdrant from 1.16.x to 1.17.x, our automated integration test failed because cosine similarity scores for top-10 search results changed from 0.892 to 0.887. Should we treat this score shift as a blocking migration bug? | pass→pass | 14,445 | 5,929 | -59% | 1 | 1 | 0% | 2,235 | 2,035 | -9% | 0 | 0 | — |
▸case-14 We have an offline backup of Qdrant binary data created on version 1.14.0. We want to restore this data directly into a fresh Qdrant 1.17.0 server instance without intermediate boots. Is direct storage compatibility guaranteed across three minor versions? | fail→pass | 11,300 | 7,644 | -32% | 1 | 1 | 0% | 1,654 | 2,401 | +45% | 0 | 0 | — |
▸case-15 We are migrating our Qdrant infrastructure from self-hosted to Qdrant Cloud. How does Qdrant Cloud change the maintenance burden when performing multi-minor-version upgrades such as moving from 1.15 to 1.17? | pass→pass | 15,860 | 9,117 | -43% | 1 | 1 | 0% | 2,458 | 2,787 | +13% | 0 | 0 | — |
▸case-16 We are planning a self-hosted upgrade step from 1.14 to 1.17 on a cluster with replication factor 3. Since each minor step requires its own rolling restart, when should this multi-step upgrade be scheduled? | pass→pass | 14,820 | 7,441 | -50% | 1 | 1 | 0% | 2,375 | 2,288 | -4% | 0 | 0 | — |
▸case-17 We are setting up a new service using Qdrant server version 1.17.2. What version branch of the Qdrant client SDK should we pin in our project dependencies? | pass→pass | 7,839 | 4,768 | -39% | 1 | 1 | 0% | 1,380 | 1,973 | +43% | 0 | 0 | — |
▸case-18 When upgrading a Qdrant database, our developer assumed that as long as the gRPC REST API schema hasn't changed, existing search queries will perform identically. What often-overlooked release note detail should be verified beyond API deprecations? | pass→pass | 13,753 | 4,999 | -64% | 1 | 1 | 0% | 1,982 | 1,895 | -4% | 0 | 0 | — |
▸case-19 Our DevOps team postpones Qdrant upgrades until forced by end-of-life status, leading to multi-year version jumps. What is the operational benefit of maintaining a regular minor version upgrade cadence? | pass→pass | 18,684 | 10,559 | -43% | 1 | 1 | 0% | 2,367 | 2,882 | +22% | 0 | 0 | — |
▸case-20 We need to filter vectors in a Qdrant collection where the field 'status' equals 'active' and 'score' is greater than 80 using the Qdrant Python SDK. How do we construct this filter query? | pass→pass | 10,236 | 6,901 | -33% | 1 | 1 | 0% | 1,486 | 2,279 | +53% | 0 | 0 | — |
▸case-21 We want to trigger a manual snapshot creation for a collection named 'documents' using Qdrant's REST API endpoint. What HTTP request method and URL path should we invoke? | pass→pass | 2,975 | 3,938 | +32% | 1 | 1 | 0% | 447 | 1,721 | +285% | 0 | 0 | — |
▸case-22 We are creating a new Qdrant collection for high-throughput search and want to configure the HNSW vector index parameters m and ef_construct. What API payload structure defines these HNSW settings under hnsw_config? | pass→pass | 8,873 | 6,167 | -30% | 1 | 1 | 0% | 1,638 | 2,464 | +50% | 0 | 0 | — |
▸case-23 In a distributed Qdrant cluster, we need to move a collection shard from node 1 to node 2 using the cluster operations API. What REST API endpoint and JSON payload command perform this shard transfer? | pass→pass | 6,163 | 6,960 | +13% | 1 | 1 | 0% | 1,206 | 2,327 | +93% | 0 | 0 | — |