Skip to content

Fix vector store showing Qdrant label for new pgvector stores#304

Merged
ckakgun merged 1 commit into
mainfrom
fix/vector-store-default-provider-label
Jul 9, 2026
Merged

Fix vector store showing Qdrant label for new pgvector stores#304
ckakgun merged 1 commit into
mainfrom
fix/vector-store-default-provider-label

Conversation

@ckakgun

@ckakgun ckakgun commented Jul 9, 2026

Copy link
Copy Markdown
Collaborator

Problem

When a new RAG vector store is created (or cloned) with a Postgres/pgvector credential, the badge in the bottom-right of the card showed "Qdrant" by default. Refreshing the page fixed it.

Cause

The create/clone handlers in VectorStoresPanel.vue build an optimistic list item but omitted the backend field. With store.backend undefined, the template's store.backend === "pgvector" ? "Postgres" : "Qdrant" fell through to the "Qdrant" default. A refresh reloaded the list from the API (which returns the correct backend), which is why it self-corrected.

Fix

Carry backend through in both optimistic list updates (createVectorStore and cloneVectorStore). The backend already returns the correct backend on both endpoints.

Testing

  • bun run typecheck passes.
  • Change is a single Vue file; no backend/logic changes.

🤖 Generated with Claude Code

Newly created and cloned vector stores were pushed into the list without
the `backend` field, so `store.backend` was undefined and the badge fell
through to the "Qdrant" default until a page refresh reloaded the list
from the API. Carry `backend` through in both optimistic list updates.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@ckakgun ckakgun force-pushed the fix/vector-store-default-provider-label branch from a183ee5 to cb36d3a Compare July 9, 2026 12:48
@ckakgun ckakgun enabled auto-merge July 9, 2026 12:52
@ckakgun ckakgun merged commit 8116321 into main Jul 9, 2026
2 checks passed
@ckakgun ckakgun deleted the fix/vector-store-default-provider-label branch July 9, 2026 12:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant