KBQA FAQ#

Q1: text2vec-large-chinese not found#

make sure you have download text2vec-large-chinese embedding model in right way

centos:yum install git-lfs
ubuntu:apt-get install git-lfs -y
macos:brew install git-lfs

cd models
git lfs clone https://huggingface.co/GanymedeNil/text2vec-large-chinese

Q2:How to change Vector DB Type in DB-GPT.#

Update .env file and set VECTOR_STORE_TYPE.

DB-GPT currently support Chroma(Default), Milvus(>2.1), Weaviate vector database. If you want to change vector db, Update your .env, set your vector store type, VECTOR_STORE_TYPE=Chroma (now only support Chroma and Milvus(>2.1), if you set Milvus, please set MILVUS_URL and MILVUS_PORT) If you want to support more vector db, you can integrate yourself.how to integrate

#*******************************************************************#
#**                  VECTOR STORE SETTINGS                       **#
#*******************************************************************#
VECTOR_STORE_TYPE=Chroma
#MILVUS_URL=127.0.0.1
#MILVUS_PORT=19530
#MILVUS_USERNAME
#MILVUS_PASSWORD
#MILVUS_SECURE=

#WEAVIATE_URL=https://kt-region-m8hcy0wc.weaviate.network

Q3:When I use vicuna-13b, found some illegal character like this.#

Set KNOWLEDGE_SEARCH_TOP_SIZE smaller or set KNOWLEDGE_CHUNK_SIZE smaller, and reboot server.

Q4:space add error (pymysql.err.OperationalError) (1054, “Unknown column ‘knowledge_space.context’ in ‘field list’”)#

1.shutdown dbgpt_server(ctrl c)

2.add column context for table knowledge_space

mysql -h127.0.0.1 -uroot -paa12345678

3.execute sql ddl

mysql> use knowledge_management;
mysql> ALTER TABLE knowledge_space ADD COLUMN context TEXT COMMENT "arguments context";

4.restart dbgpt serve

Q5:Use Mysql, how to use DB-GPT KBQA#

build Mysql KBQA system database schema.

$ mysql -h127.0.0.1 -uroot -paa12345678 < ./assets/schema/knowledge_management.sql

Q6:when pull from 0.4.0, I found historical knowledge document disappeared#

In version 0.4.0, the metadata module of the DB-GPT application has been refactored. All metadata tables will now be automatically saved in the ‘dbgpt’ database, based on the database type specified in the .env file. If you would like to retain the existing data, it is recommended to use a data migration tool to transfer the database table information to the ‘dbgpt’ database. Additionally, you can change the default database name ‘dbgpt’ in your .env file.

Tip

old database:knowledge_management; new database:dbgpt;

### SQLite database (Current default database)
#LOCAL_DB_PATH=data/default_sqlite.db
#LOCAL_DB_TYPE=sqlite

### Mysql database
LOCAL_DB_TYPE=mysql
LOCAL_DB_USER=root
LOCAL_DB_PASSWORD=aa12345678
LOCAL_DB_HOST=127.0.0.1
LOCAL_DB_PORT=3306
# You can change it to your actual metadata database name
LOCAL_DB_NAME=dbgpt