DB Weekly: Docker patch boundaries, StructArray semantics, and vector-search tuning

At a glance

MySQL: patch the deployment boundary you actually run

Milvus 3.0 StructArray: schema shape becomes query semantics

• Entity-level EmbeddingList search: Milvus compares a query list with the stored list through a MAX_SIM* metric and returns the parent entity.
• Same-element filtering: MATCH_ANY, MATCH_ALL, MATCH_LEAST, MATCH_MOST, and MATCH_EXACT evaluate predicates at each element offset. A kitchen label and a confidence threshold therefore apply to the same clip rather than to two unrelated clips in one parent entity.
• Element-level search: A regular vector query against a subfield such as clips[clip_embedding] returns the parent entity together with the zero-based offset of the matching element. An element_filter can limit the participating elements.

Qdrant: tune the failure mode before tuning the knob

• A candidate limit increase from 10 to 500 improved the best achievable score by up to 0.28, while the score visible to users moved by at most 0.01. The retrieval stage had found relevant documents, and the ranking stage had buried them.
• Changing hnsw_ef moved the final score by at most 0.0022 in the report's runs. That result makes hnsw_ef a poor first experiment when the real problem is downstream ranking.
• Changing reciprocal rank fusion k from 2 to 61 changed the top-ranked result on 202 of 480 queries in one dataset. Qdrant's parameter-free DBSF fusion beat default RRF on 3 of 5 datasets.
• The best of four tested rerankers beat out-of-the-box fusion on all five datasets. Against tuned fusion, most of that gain disappeared, and one reranker win became a loss.
• Quantization rescoring changed one query from 4.3 ms to 43.4 ms after the original vectors crossed the memory boundary. Without rescoring, the dense stage found only 6 in 10 true nearest neighbors in the cited test.

Evidence gaps for this window

Cross-engine positioning

1. Deployment and security: MySQL's public notes define which artifact the release covers. The first question is patch applicability.
2. Data model and result identity: Milvus StructArray defines whether the application searches a parent entity or an element inside it. The first question is schema and API behavior.
3. Workload behavior: Qdrant's report shows how candidate depth, fusion, reranking, and memory pressure interact on five datasets. The first question is which failure mode the workload exhibits.

Action queue

1. Patch MySQL artifacts in scope. Inventory MySQL Server Docker images, Connector/ODBC packages, MySQL Shell, and Cluster surfaces separately. Apply the supported patch path, then test startup, replication, authentication, and application connectivity.
2. Prototype StructArray with real result contracts. Model one parent record with several aligned elements. Test parent-level retrieval, element offsets, same-element predicates, and response collapsing before planning a data migration.
3. Build a retrieval evaluation set. Use production failure queries, label enough examples to distinguish noise from improvement, and keep retrieval recall separate from final ranking quality.
4. Tune Qdrant in cost order. Check collection settings, candidate depth, and fusion before adding reranker inference or changing the RAM-versus-rescoring trade-off.
5. Keep the cross-engine shortlist open. Reserve a selection change for a matched benchmark or a production migration report with comparable workload, environment, outcome, and methodology. This week's evidence earns targeted validation work, not a leaderboard rewrite.