Skip to content

docs(config): document Qdrant connection block and complete openGauss tuning fields#2375

Open
r266-tech wants to merge 2 commits into
volcengine:mainfrom
r266-tech:docs-vectordb-qdrant-opengauss-config-2350-2367
Open

docs(config): document Qdrant connection block and complete openGauss tuning fields#2375
r266-tech wants to merge 2 commits into
volcengine:mainfrom
r266-tech:docs-vectordb-qdrant-opengauss-config-2350-2367

Conversation

@r266-tech
Copy link
Copy Markdown
Contributor

The recently merged Qdrant backend (#2350) and openGauss persistence improvements (#2367) shipped config fields that the vectordb section of docs/{en,zh}/guides/01-configuration.md doesn't yet cover:

  • Qdrant: the backend is registered and QdrantCollectionAdapter.from_config reads url/api_key/timeout_seconds/dense_vector_name/sparse_vector_name/meta_collection_name/enable_text_index, but there is no qdrant connection example <details> (the comparable openGauss remote backend has a full one). Added one mirroring the openGauss block, using the defaults from QdrantConfig.
  • openGauss: the existing example only shows host/port/user/password/db_name/schema/mode; added the shipped tuning fields shard_count/connect_timeout/dense_vector_name/sparse_vector_name (all real Field(...) defaults in OpenGaussConfig) and noted shard_count in the distributed clause.

Pure docs, EN + ZH mirrored. Field names and defaults verified against openviking_cli/utils/config/vectordb_config.py.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 1, 2026

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis ✅

2350 - Fully compliant

Compliant requirements:

  • Added Qdrant backend configuration documentation in English and Chinese

2367 - Fully compliant

Compliant requirements:

  • Added missing openGauss tuning fields to documentation in English and Chinese
⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪
🏅 Score: 100
🧪 No relevant tests
🔒 No security concerns identified
✅ No TODO sections
🔀 No multiple PR themes
⚡ No major issues detected

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 1, 2026

PR Code Suggestions ✨

No code suggestions found for the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

1 participant