feat: bfb update-collection

[tellet-q]

Note: base is not dev! Only merge after #156

Apply a partial collection-config patch and wait for the optimization — a common benchmark shape.

bfb upload --file config.yaml -n 1M --skip-wait-index   # indexing_threshold: 1000000000
bfb update-collection --file examples/update-config.yaml --json index.json

collection:                                                                                                                                                                                                                                 
  name: benchmark                                                                                                                                                                                                                           
  optimizers:                                                                                                                                                                                                                               
    indexing_threshold: 1        # start indexing now
    # max_segment_size: 200000   # changing this triggers a merge

Updated collection: optimizers.indexing_threshold=1

Server reported changes: true
Index ready in 20.255 seconds

Only declared keys are sent — undeclared ≠ false/0, so the rest of the config is left alone. The patch request returns before the work finishes, so this waits and reports it the way bfb upload does: the patch lands under results.update_collection, the triggered indexing under results.index. A no-op patch is an error, not a silent success; --skip-wait-index fires and returns without waiting.

[Copilot]

Pull request overview

Adds a new bfb update-collection subcommand to apply a partial, YAML-defined collection settings patch to an existing Qdrant collection, then (optionally) wait for and measure the indexing work that the patch triggers—mirroring how bfb upload reports indexing waits.

Changes:

• Introduces update-collection CLI plumbing and JSON result reporting (results.update_collection, with triggered indexing under results.index).
• Adds a YAML “patch” config format where all fields are optional, so only declared keys are sent to the server.
• Documents the new workflow and adds an example update config file.

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
src/results.rs	Adds UpdateCollectionPhase and wires it into the per-phase JSON results structure.
src/main.rs	Implements run_update_collection and dispatches the new subcommand.
src/config/update.rs	New YAML patch config schema + validation (rejects patches that declare no fields) + unit tests.
src/config/mod.rs	Exposes the new config::update module.
src/collection/mod.rs	Implements the Qdrant update_collection call builder and reporting of the patch operation.
src/args/mod.rs	Adds the UpdateCollection subcommand and its --file argument.
README.md	Documents update-collection behavior, outputs, and JSON fields.
examples/update-config.yaml	Provides an example patch file for common benchmark workflows.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.