feat: expose KB ↔ vector store binding in list, editor, and detail UI

Backend
-------
ListKnowledgeBases now enriches each row with the resolved vector_store
metadata (name / source / engine_type / status) via a new
buildKBListResponse helper. Store views are batch-resolved once per
request through BatchResolveStoreView so an N-KB list costs one
vector-store service call rather than N — closing the N+1 limitation
flagged in #1372's known-limitations section. Cross-tenant shared KBs
continue to render via SharedStoreDisplay so the owning tenant's store
inventory cannot be correlated across rows; the underlying vector_store_id
UUID is stripped from those responses.

Resolver failures degrade gracefully: bound KBs render as unavailable
instead of breaking the list. Test coverage pins the env / bound /
shared distinction, the batch-call-count invariant, and the
graceful-failure path.

Frontend
--------
KB editor modal gains a new "Vector Store" section. Create mode shows a
dropdown that combines the system default (env store) and the tenant's
configured user stores, fetched once at mount via the existing
listVectorStores API. Edit mode shows the bound store read-only via a
new VectorStoreBadge component with an explicit immutability hint —
matching the backend's `<-:create` GORM tag and the service-layer
UpdateKnowledgeBaseRequest DTO that already omit the field.

KB list cards surface a small engine-type badge for own-tenant bound
KBs, and a warning badge when the bound store is unavailable. Env-bound
and shared KBs render no badge (visual noise control). KB detail header
shows the bound store via the same VectorStoreBadge component; shared
KBs fall through to the badge's internal "shared" branch with no name /
engine / id rendered.

The KB editor's create-time error handler translates the typed
ErrVectorStoreBindingInvalid (2200) and ErrVectorStoreUnavailable
(2201) into localized messages and jumps the user back to the
VectorStore section so they can pick a different store or fall back to
the system default.

The KB row type gains five optional fields (vector_store_id / name /
engine_type / source / status). i18n: 18 new keys added to en-US,
ko-KR, zh-CN; ru-RU receives English placeholders pending translation
(consistent with prior PRs in this locale).

Part of #993 (Phase 2: Per-KB VectorStore Binding).
Phase 2 roadmap item: PR 5 (KB binding UI + list-response enrichment).
Depends on #994, #1310, #1372, #1386 (all backend in the Phase 2 series).
This commit is contained in:
ochan.kwon
2026-05-18 23:50:09 +09:00
committed by lyingbug
parent 0f57bf3ff8
commit 8b7d00b260
15 changed files with 1165 additions and 12 deletions
@@ -152,6 +152,20 @@
/>
</div>
<!-- VectorStore 绑定 -->
<div v-show="currentSection === 'vectorStore'" class="section">
<KBVectorStoreSettings
v-if="formData"
:mode="mode"
:vector-store-id="formData.vectorStoreId"
:bound-source="formData.vectorStoreInfo?.source"
:bound-name="formData.vectorStoreInfo?.name"
:bound-engine-type="formData.vectorStoreInfo?.engineType"
:bound-status="formData.vectorStoreInfo?.status"
@update:vector-store-id="handleVectorStoreIdUpdate"
/>
</div>
<!-- FAQ 配置 -->
<div v-if="isFAQ && formData" v-show="currentSection === 'faq'" class="section">
<div class="section-content">
@@ -365,6 +379,7 @@ import KBModelConfig from './settings/KBModelConfig.vue'
import KBParserSettings from './settings/KBParserSettings.vue'
import KBStorageSettings from './settings/KBStorageSettings.vue'
import KBChunkingSettings from './settings/KBChunkingSettings.vue'
import KBVectorStoreSettings from './settings/KBVectorStoreSettings.vue'
import KBAdvancedSettings from './settings/KBAdvancedSettings.vue'
import ModelSelector from '@/components/ModelSelector.vue'
import GraphSettings from './settings/GraphSettings.vue'
@@ -398,8 +413,9 @@ const hasFiles = ref(false)
const initialStorageProvider = ref<string>('')
const initialIndexingStrategy = ref<any>(null)
const dsCount = ref(0)
// KB.creator_id (added in PR 5). Empty for legacy KBs — those fall back
// to "no owner", so only tenant Admin+ can mutate share settings.
// Identifier of the user who created this KB. Empty for older rows
// that predate per-KB ownership tracking; those KBs have no "owner" and
// only tenant Admin+ can mutate their share settings.
const kbCreatorId = ref<string>('')
// Backend gate for /knowledge-bases/:id/shares (POST/PUT/DELETE) is
@@ -437,7 +453,11 @@ const DEFAULT_CHUNKING_PRESET = {
const navItems = computed(() => {
const items: { key: string; icon: string; label: string; badge?: number }[] = [
{ key: 'basic', icon: 'info-circle', label: t('knowledgeEditor.sidebar.basic') },
{ key: 'models', icon: 'control-platform', label: t('knowledgeEditor.sidebar.models') }
{ key: 'models', icon: 'control-platform', label: t('knowledgeEditor.sidebar.models') },
// VectorStore binding section — present in both create and edit
// modes. Create mode shows a dropdown; edit mode shows the bound
// store read-only with an immutability hint.
{ key: 'vectorStore', icon: 'data-base', label: t('knowledgeEditor.sidebar.vectorStore') }
]
if (formData.value?.type === 'faq') {
items.push({ key: 'faq', icon: 'help-circle', label: t('knowledgeEditor.sidebar.faq') })
@@ -555,6 +575,16 @@ const initFormData = (type: 'document' | 'faq' = 'document') => {
wikiEnabled: false,
graphEnabled: false,
},
// Vector-store binding. Empty string means "use the env-configured
// store"; create mode defaults to that, edit mode loads the
// existing binding from the KB response below.
vectorStoreId: '' as string,
vectorStoreInfo: {
source: undefined as string | undefined,
name: undefined as string | undefined,
engineType: undefined as string | undefined,
status: undefined as string | undefined,
},
}
}
@@ -661,6 +691,19 @@ const loadKBData = async () => {
wikiEnabled: kb.indexing_strategy?.wiki_enabled ?? false,
graphEnabled: kb.indexing_strategy?.graph_enabled ?? false,
},
// Vector-store binding. vectorStoreId is editor-only state; it
// is only included in the create request, never the update
// request, because the binding is immutable after creation.
// vectorStoreInfo carries the read-only display fields that the
// edit view renders below; they come straight from the KB
// response.
vectorStoreId: '',
vectorStoreInfo: {
source: kb.vector_store_source,
name: kb.vector_store_name,
engineType: kb.vector_store_engine_type,
status: kb.vector_store_status,
},
}
initialStorageProvider.value = formData.value.storageProvider
initialIndexingStrategy.value = { ...formData.value.indexingStrategy }
@@ -793,6 +836,16 @@ const handleStorageProviderUpdate = (value: string) => {
}
}
const handleVectorStoreIdUpdate = (id: string) => {
if (formData.value) {
// Empty string here means "use system default" (env-store fallback).
// The create-payload assembly below converts this back to `omit` so
// the backend stores NULL — keeping the wire shape identical to
// pre-Phase-2 clients.
formData.value.vectorStoreId = id || ''
}
}
const handleQuestionGenerationUpdate = (config: any) => {
if (formData.value) {
formData.value.questionGenerationConfig = { ...config }
@@ -886,6 +939,15 @@ const buildSubmitData = () => {
summary_model_id: formData.value.modelConfig.llmModelId
}
// Vector-store binding. Only attach the field when the user actively
// selected a non-default store. The server treats an empty string as
// NULL, but keeping the field absent on the wire matches what a
// client that doesn't know about this binding would send — which
// makes A/B response diffs easier to read.
if (formData.value.vectorStoreId) {
data.vector_store_id = formData.value.vectorStoreId
}
// 添加多模态配置
data.vlm_config = {
enabled: formData.value.multimodalConfig.enabled,
@@ -1130,7 +1192,23 @@ const doSubmit = async () => {
handleClose()
} catch (error: any) {
console.error('Knowledge base operation failed:', error)
MessagePlugin.error(error?.message || t('common.operationFailed'))
// Vector-store-binding error codes from the server. Both indicate
// the selected store cannot be used: 2200 is "the binding itself
// is invalid" (e.g. unknown id, foreign tenant), 2201 is "the
// store is currently unreachable". For either, swap in a localized
// message and jump the user back to the Vector Store section so
// they can pick a different store or fall back to the system
// default.
const code = error?.response?.data?.error?.code ?? error?.code
if (code === 2200) {
MessagePlugin.error(t('knowledgeEditor.errors.vectorStoreBindingInvalid'))
currentSection.value = 'vectorStore'
} else if (code === 2201) {
MessagePlugin.error(t('knowledgeEditor.errors.vectorStoreUnavailable'))
currentSection.value = 'vectorStore'
} else {
MessagePlugin.error(error?.message || t('common.operationFailed'))
}
} finally {
saving.value = false
}