You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 30, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: docs/docs/03-architecture.md
+4-6Lines changed: 4 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,12 +22,10 @@ You can make use of it in the CLI by setting the `KNOW_SERVER_URL` environment v
22
22
## 3. Index Database
23
23
24
24
The index database is an additional (relational) metadata database which keeps track of all datasets and ingested files and their relationships.
25
-
It enables some extra convenience features but does not store the actual data (embeddings).
26
-
The current implementation uses **SQLite**.
27
-
It's fully embedded and does not require any additional setup.
25
+
It enables some extra convenience features but does not store the actual data (content & embeddings).
26
+
The current implementation uses **SQLite** by default, which is fully embedded and does not require any additional setup.
28
27
29
28
## 4. Vector Database
30
29
31
-
The vector database is the main storage for the embeddings of the ingested documents along with some metadata (e.g. source file information).
32
-
The current implementation uses [**chromem-go**](https://github.com/philippgille/chromem-go).
33
-
It's fully embedded and does not require any additional setup.
30
+
The vector database is the main storage for the content and embeddings of the ingested documents along with some metadata (e.g. source file information).
31
+
The current implementation uses [**chromem-go**](https://github.com/philippgille/chromem-go) by default, which is fully embedded and does not require any additional setup.
The vector database is the main storage for the content and embeddings of the ingested documents along with some metadata (e.g. source file information).
23
+
The current implementation uses [**chromem-go**](https://github.com/philippgille/chromem-go) by default, which is fully embedded and does not require any additional setup.
24
+
25
+
You can configure it by setting a database connection string via the `KNOW_VECTOR_DSN` environment variable.
26
+
The following options are available:
27
+
28
+
-[Chromem-Go](https://github.com/philippgille/chromem-go) (default): `KNOW_VECTOR_DSN="chromem:///path/to/directory"` (Note: we're using a customized fork of chromem-go, so some details may differ from the original project)
0 commit comments