Quick Start
How It Works
ClickHouse is a knowledge store (vector search), not a primary conversation backend. Pair it with SQLite or PostgreSQL for chat history viadb().
Configuration Options
| Option | Type | Default | Description |
|---|---|---|---|
host | str | "localhost" | ClickHouse server hostname |
port | int | 8123 | HTTP port |
username | str | "default" | Database username |
password | str | "" | Database password |
database | str | "praisonai" | Database name (created if missing) |
secure | bool | False | Use HTTPS connection |
CLICKHOUSE_HOST, CLICKHOUSE_PORT, CLICKHOUSE_USER, CLICKHOUSE_PASSWORD.
Docker Setup
Best Practices
Use ClickHouse for knowledge, not conversations
Use ClickHouse for knowledge, not conversations
Store embeddings and retrieval in ClickHouse; keep conversation history in PostgreSQL, MySQL, or SQLite.
Batch inserts for throughput
Batch inserts for throughput
Insert documents in batches of 1000+ rows for better write performance on large corpora.
Partition large tables by time
Partition large tables by time
Use
PARTITION BY toYYYYMM(timestamp) when logging retrieval events for analytics.Set secure=True in production
Set secure=True in production
Enable TLS and authentication when connecting to remote ClickHouse clusters.
Related
Database Persistence
Compare all persistence backends
Persistence Backend Plugins
Register custom storage backends

