Skip to main content
Lakehouse integration can be enabled or disabled at the cluster, namespace, and topic levels using dynamic configuration. This allows fine-grained control over which topics produce lakehouse tables.
For the full set of dynamic configuration keys (including topic-level feature settings such as partitionKey and upsertModeEnabled), see the Dynamic Configuration Guide.

Table Modes

Compaction task publishing is enabled when either sdt.enabled or sbt.enabled is true.

Configuration Key Format

All dynamic configuration keys must be prefixed with the cluster name. The cluster name is the value of clusterName in the Pulsar broker’s conf/broker.conf. See Finding the Cluster Name for how to retrieve it. For example, if the cluster name is private-cloud:

Supported Dynamic Configuration Keys

Cluster Level

Applied via the sn/system namespace:

Namespace and Topic Level

Cluster-Level Configuration

Cluster-level properties are stored in the sn/system namespace.

Enable SDT for the cluster

Set the default catalog

Namespace-Level Configuration

Enable SDT for a namespace

Assign a catalog to a namespace

Example:

Topic-Level Configuration

Topic-level properties override namespace-level settings.

Enable SDT for a topic

Assign a catalog to a topic

Example:

Configuration Override Priority

Settings at a more specific level override broader settings:

Extending Valid Configuration Keys

To introduce additional dynamic configuration keys, set the following environment variable when starting the Pulsar broker:
Example:

Next Steps