Table Types

KalamDB uses four runtime table types:

• USER
• SHARED
• STREAM
• SYSTEM (internal)

Table-Type Routing Model

Quick Selection

• choose USER for tenant/user-isolated data
• choose SHARED for global application data
• choose STREAM for short-lived realtime event state
• treat SYSTEM as internal metadata tables managed by the engine

SQL Creation Patterns

Recommended unified syntax:

1CREATE TABLE app.messages (2  id BIGINT PRIMARY KEY DEFAULT SNOWFLAKE_ID(),3  content TEXT NOT NULL,4  created_at TIMESTAMP DEFAULT NOW()5) WITH (TYPE = 'USER');

Also supported for compatibility:

• CREATE USER TABLE ...
• CREATE SHARED TABLE ...
• CREATE STREAM TABLE ...

USER Tables

Per-user logical isolation with user-aware routing and permissions.

1CREATE TABLE chat.messages (2  id BIGINT PRIMARY KEY DEFAULT SNOWFLAKE_ID(),3  conversation_id BIGINT NOT NULL,4  content TEXT NOT NULL,5  created_at TIMESTAMP DEFAULT NOW()6) WITH (7  TYPE = 'USER',8  FLUSH_POLICY = 'rows:1000,interval:60',9  STORAGE_ID = 'local'10);

Use for: conversations, preferences, private records, tenant data.

SHARED Tables

Global shared scope for all users.

1CREATE TABLE app.config (2  key TEXT PRIMARY KEY,3  value TEXT NOT NULL,4  updated_at TIMESTAMP DEFAULT NOW()5) WITH (6  TYPE = 'SHARED',7  ACCESS_LEVEL = 'PRIVATE'8);

Use for: reference data, global settings, shared catalogs.

STREAM Tables

Ephemeral rows with TTL-based eviction. Like USER tables, STREAM tables are scoped per user tenant and are not shared across all users.

1CREATE TABLE chat.typing_events (2  event_id BIGINT PRIMARY KEY DEFAULT SNOWFLAKE_ID(),3  user_id TEXT NOT NULL,4  event_type TEXT NOT NULL,5  created_at TIMESTAMP DEFAULT NOW()6) WITH (7  TYPE = 'STREAM',8  TTL_SECONDS = 309);

Use for: typing indicators, presence, cursor events, transient signals.

Realtime Subscriptions

Today, KalamDB supports realtime subscriptions to all three primary application table types: USER, SHARED, and STREAM. This allows applications to listen for live changes (inserts, updates, deletes) as they happen, enabling reactive UIs and realtime workflows.

Subscriptions can be full-row (SELECT *) or projected (SELECT username, status FROM chat.changes ...) depending on the payload shape your client needs.

SYSTEM Tables

Internal control-plane and metadata tables (system.*).

• not intended for normal app DDL lifecycle
• role-restricted access for sensitive operations
• file upload/download flows reject SYSTEM tables

Capability Matrix

Capability Definitions

• App DDL creation: Whether application SQL can create/manage this table type directly.
• Per-user isolation: Whether data is automatically isolated by authenticated user/tenant.
• ACCESS_LEVEL option: Whether table-level access policy can be configured through ACCESS_LEVEL.
• TTL_SECONDS option: Whether the table supports TTL-based automatic row eviction.
• USE_USER_STORAGE option: Whether table storage can be explicitly pinned to user-scoped storage paths.
• Cold-tier Parquet lifecycle: Whether hot data can flush/compact into cold-tier Parquet segments.
• File APIs supported: Whether /v1/files/... upload/download flows are supported for rows in this table type.
• Live Query: Whether realtime subscriptions can stream change events from this table type.
• Cluster multi-group Raft support: Whether metadata/data operations for this table type participate in clustered Raft replication groups.

Related Docs

• Table DDL
• Storage Tiers
• FILE Datatype
• File - Upload & DataType
• Storage ID Usage