Server configuration¶

These configuration parameters control the general behavior of ksqlDB server. Many parameters can only be set once for the entire server, and must be specified using the ksql-server.properties file (for on-prem / standalone). In this case, configurations are applied when the cluster starts.

A subset of these configuration parameters can be applied on a running cluster, either for individual queries (using the SET command or the Confluent Cloud Console) or for the entire cluster (using the ALTER SYSTEM command or the Confluent Cloud Console). When this is the case for a parameter, it is called out in the parameter description's Per query block. Currently, you can edit parameters in this subset only in Confluent Cloud.

You can assign the value of some parameters on a per-persistent query basis by using the SET statement. This is indicated in the following parameter sections with the Per query block. For ksqlDB in Confluent Cloud, some parameters can be set only by using the ALTER SYSTEM statement and are applied to all queries running on the current cluster, as indicated in the corresponding Per query block.

Note

You can change per-query configs by using the SET statement, but you must also redeploy the query with CREATE OR REPLACE or by deleting the query and recreating it.

Retrieve the current list of configuration settings by using the SHOW PROPERTIES command.

For more information on setting properties, see Configure ksqlDB Server.

Important

ksqlDB Server configuration settings take precedence over those set in the ksqlDB CLI. For example, if a value for ksql.streams.replication.factor is set in both ksqlDB Server and ksqlDB CLI, the ksqlDB Server value is used.

Tip

Each property has a corresponding environment variable in the Docker image for ksqlDB Server. The environment variable name is constructed from the configuration property name by converting to uppercase, replacing periods with underscores, and prepending with KSQL_. For example, the name of the ksql.service.id environment variable is KSQL_KSQL_SERVICE_ID. For more information, see Install ksqlDB with Docker.

Info

The underlying producer and consumer clients in ksqlDB's server can be modified with any valid properties. Simply use the form ksql.streams.producer.xxx, ksql.streams.consumer.xxx to pass the property through. For example, ksql.streams.producer.compression.type sets the compression type on the producer.

`compression.type`¶

Per query: no

Sets the compression type used by Kafka producers, like the INSERT VALUES statement. The default is snappy.

This setting is distinct from the ksql.streams.producer.compression.type config, which sets the type of compression used by streams producers for topics created by CREATE TABLE AS SELECT, CREATE STREAM AS SELECT, and INSERT INTO statements.

`ksql.advertised.listener`¶

Per query: no

This is the URL used for inter-node communication. Unlike listeners or ksql.internal.listener, this configuration doesn't create a listener. Instead, it is used to set an externally routable URL that other ksqlDB nodes will use to communicate with this node. It only needs to be set if the internal listener is not externally resolvable or routable.

If not set, the default behavior is to use the internal listener, which is controlled by ksql.internal.listener.

If ksql.internal.listener resolves to a URL that uses localhost, a wildcard IP address, like 0.0.0.0, or a hostname that other ksqlDB nodes either can't resolve or can't route requests to, set ksql.advertised.listener to a URL that ksqlDB nodes can resolve.

For more information, see Configuring Listeners of a ksqlDB Cluster

`ksql.assert.schema.default.timeout.ms`¶

The amount of time an ASSERT SCHEMA statement will wait for the assertion to succeed if no timeout is specified.

`ksql.assert.topic.default.timeout.ms`¶

The amount of time an ASSERT TOPIC assertion will wait for the assertion to succeed if no timeout is specified.

`ksql.connect.url`¶

Per query: no

The Connect cluster URL to integrate with. If the Connect cluster is running locally to the ksqlDB Server, use localhost and the configuration port specified in the Connect configuration file.

`ksql.connect.worker.config`¶

Per query: no

The connect worker configuration file, if spinning up Connect alongside the ksqlDB server. Don't set this property if you're using an external ksql.connect.url.

`ksql.extension.dir`¶

Per query: no

The directory in which ksqlDB looks for UDFs. The default value is the ext directory relative to ksqlDB's current working directory.

`ksql.fail.on.deserialization.error`¶

Per query: no

Indicates whether to fail if corrupt messages are read. ksqlDB decodes messages at runtime when reading from a Kafka topic. The decoding that ksqlDB uses depends on what's defined in STREAM's or TABLE's data definition as the data format for the topic. If a message in the topic can't be decoded according to that data format, ksqlDB considers this message to be corrupt.

For example, a message is corrupt if ksqlDB expects message values to be in JSON format, but it's in DELIMITED format instead. The default value in ksqlDB is false, which means a corrupt message results in a log entry, and ksqlDB continues processing. To change this default behavior and instead have Kafka Streams threads shut down when corrupt messages are encountered, add the following setting to your ksqlDB Server properties file:

`ksql.fail.on.production.error`¶

Per query: no

Indicates whether to fail if ksqlDB fails to publish a record to an output topic due to a Kafka producer exception. The default value in ksqlDB is true, which means if a producer error occurs, then the Kafka Streams thread that encountered the error will shut down. To log the error message to the Processing Log and have ksqlDB continue processing as normal, add the following setting to your ksqlDB Server properties file:

ksql.fail.on.production.error=false

`ksql.functions.<UDF Name>.<UDF Config>`¶

Per query: no

Makes custom configuration values available to the UDF specified by name. For example, if a UDF is named "formula", you can pass a config to that UDF by specifying the ksql.functions.formula.base.value property. Access the property in the UDF's configure method by using its full name, ksql.functions.formula.base.value. This example is explored in detail here.

`ksql.functions.collect_list.limit`¶

Per query: no

Limit the size of the resultant Array to N entries, beyond which any further values are silently ignored, by setting this configuration to N.

For more information, see aggregate-functions.

Note

In Confluent Cloud, the ksql.functions.collect_list.limit config is set to 1000 and can't be changed.

`ksql.functions.collect_set.limit`¶

Per query: no

Limits the size of the resultant Set to N entries, beyond which any further values are silently ignored, by setting this configuration to N.

For more information, see aggregate-functions.

Note

In Confluent Cloud, the ksql.functions.collect_set.limit config is set to 1000 and can't be changed.

`ksql.endpoint.logging.log.queries`¶

Per query: no

Whether or not to log the query portion of the URI when logging endpoints. Note that enabling this may log sensitive information.

`ksql.endpoint.logging.ignored.paths.regex`¶

Per query: no

A regex that allows users to filter out logging from certain endpoints. Without this filter, all endpoints are logged. An example usage of this configuration would be to disable heartbeat logging, for example, ksql.endpoint.logging.ignored.paths.regex=.heartbeat., which can otherwise be verbose. Note that this works on the entire URI, respecting the ksql.endpoint.logging.log.queries configuration)

`ksql.heartbeat.enable`¶

Per query: no

If enabled, ksqlDB servers in the same ksqlDB cluster send heartbeats to each other, to aid in faster failure detection for improved pull query routing. Also enables the /clusterStatus endpoint. The default is false.

Important

Be careful when you change heartbeat configuration values, because the stability and availability of ksqlDB applications depend sensitively on them. For example, if you set the value of ksql.heartbeat.check.interval.ms too high, it takes longer for nodes to determine the availability of actives and standbys, which may cause pull queries to fail unnecessarily.

`ksql.heartbeat.send.interval.ms`¶

Per query: no

If heartbeats are enabled, this config controls the interval, in milliseconds, at which heartbeats are sent between nodes. The default value is 100.

If you tune this value, also consider tuning ksql.heartbeat.check.interval.ms, which controls how often a node processes received heartbeats, and ksql.heartbeat.window.ms, which controls the window size for checking if heartbeats were missed and deciding whether a node is up or down.

`ksql.heartbeat.check.interval.ms`¶

Per query: no

If heartbeats are enabled, this config controls the interval, in milliseconds, at which a ksqlDB node processes its received heartbeats to determine whether other nodes in the cluster are down. The default value is 200.

`ksql.heartbeat.window.ms`¶

Per query: no

If heartbeats are enabled, this config controls the size of the window, in milliseconds, at which heartbeats are processed to determine how many have been missed. The default value is 2000.

`ksql.heartbeat.missed.threshold.ms`¶

Per query: no

If heartbeats are enabled, this config determines how many consecutive missed heartbeats flag a ksqlDB node as down. The default value is 3.

`ksql.heartbeat.discover.interval.ms`¶

Per query: no

If heartbeats are enabled, this config controls the interval, in milliseconds, at which a ksqlDB node checks for changes in the cluster, like newly added nodes. The default value is 2000.

`ksql.heartbeat.thread.pool.size`¶

Per query: no

If heartbeats are enabled, this config controls the size of the thread pool used for processing and sending heartbeats as well as determining changes in the cluster. The default value is 3.

`ksql.internal.listener`¶

Per query: no

The ksql.internal.listener setting controls the address bound for use by internal, intra-cluster communication.

If not set, the internal listener defaults to the first listener defined by listeners.

This setting is most often useful in an IaaS environment to separate external-facing traffic from internal traffic.

`ksql.internal.topic.replicas`¶

Per query: no

The number of replicas for the internal topics created by ksqlDB Server. The default is 1. Replicas for the record processing log topic should be configured separately. For more information, see Processing Log.

`ksql.lag.reporting.enable`¶

Per query: no

If enabled, ksqlDB servers in the same ksqlDB cluster send state-store lag information to each other as a form of heartbeat, for improved pull query routing. Only applicable if ksql.heartbeat.enable is also set to true. The default is false.

`ksql.logging.processing.topic.auto.create`¶

Per query: no

Toggles automatic processing log topic creation. If set to true, ksqlDB automatically tries to create a processing log topic at startup. The name of the topic is the value of the ksql.logging.processing.topic.name property. The number of partitions is taken from the ksql.logging.processing.topic.partitions property , and the replication factor is taken from the ksql.logging.processing.topic.replication.factor property. By default, this property has the value false.

`ksql.logging.processing.topic.name`¶

Per query: no

If automatic processing log topic creation is enabled, ksqlDB sets the name of the topic to the value of this property. If automatic processing log stream creation is enabled, ksqlDB uses this topic to back the stream. By default, this property has the value <service id>ksql_processing_log, where <service id> is the value of the ksql.service.id property.

`ksql.logging.processing.topic.partitions`¶

Per query: no

If automatic processing log topic creation is enabled, ksqlDB creates the topic with the number of partitions set to the value of this property. By default, this property has the value 1.

`ksql.logging.processing.topic.replication.factor`¶

Per query: no

If automatic processing log topic creation is enabled, ksqlDB creates the topic with the number of replicas set to the value of this property. By default, this property has the value 1.

`ksql.logging.processing.stream.auto.create`¶

Per query: no

Toggles automatic processing log stream creation. If set to true, and ksqlDB is running in interactive mode on a new cluster, ksqlDB automatically creates a processing log stream when it starts up. The name for the stream is the value of the ksql.logging.processing.stream.name property. The stream is created over the topic set in the ksql.logging.processing.topic.name property By default, this property has the value false.

`ksql.logging.processing.stream.name`¶

Per query: no

If automatic processing log stream creation is enabled, ksqlDB sets the name of the stream to the value of this property. By default, this property has the value KSQL_PROCESSING_LOG.

`ksql.logging.processing.rows.include`¶

Per query: no

Toggles whether or not the processing log should include rows in log messages. By default, this property has the value false.

Important

In Confluent Cloud, ksql.logging.processing.rows.include is set to true, so the default behavior is to include row data in the processing log. It can be configured manually when provisioning the cluster in Confluent Cloud by toggling Hide row data in processing log when provisioning in the UI, or by setting the log-exclude-rows flag in the CLI.

`ksql.logging.server.rate.limited.response.codes`¶

Per query: no

A list of code:qps pairs, to limit the rate of server request logging. An example would be "400:10" which would limit 400 error logs to 10 per second. This is useful for limiting certain 4XX errors that you might not want to blow up in the logs. This setting enables seeing the logs when the request rate is low and dropping them when they go over the threshold. A message will be logged every 5 seconds indicating if the rate limit is being hit, so an absence of this message means a complete set of logs.

`ksql.logging.server.rate.limited.request.paths`¶

Per query: no

A list of path:qps pairs, to limit the rate of server request logging. An example would be "/query:10" which would limit pull query logs to 10 per second. This is useful for requests that are coming in at a high rate, such as for pull queries. This setting enables seeing the logs when the request rate is low and dropping them when they go over the threshold. A message will be logged every 5 seconds indicating if the rate limit is being hit, so an absence of this message means a complete set of logs.

`ksql.metrics.tags.custom`¶

Per query: no

A list of tags to be included with emitted JMX metrics, formatted as a string of key:value pairs separated by commas. For example, key1:value1,key2:value2.

`ksql.output.topic.name.prefix`¶

Per query: no

The default prefix for automatically created topic names. Unless a user defines an explicit topic name in a SQL statement, ksqlDB prepends the value of ksql.output.topic.name.prefix to the names of automatically created output topics. For example, you might use "ksql-interactive-" to name output topics in a ksqlDB Server cluster that's deployed in interactive mode. For more information, see Interactive ksqlDB clusters.

`ksql.persistence.default.format.key`¶

Per query: no

Sets the default value for the KEY_FORMAT property if one is not supplied explicitly in CREATE TABLE or CREATE STREAM statements.

The default value for this configuration is KAFKA.

If not set and no explicit key format is provided in the statement, via either the KEY_FORMAT or the FORMAT property, the statement will be rejected as invalid.

For supported formats, see Serialization Formats.

CREATE STREAM AS SELECT and CREATE TABLE AS SELECT statements that create streams or tables with key columns, where the source stream or table has a NONE key format, will also use the default key format set in this configuration if no explicit key format is declared in the WITH clause.

`ksql.persistence.default.format.value`¶

Per query: no

Sets the default value for the VALUE_FORMAT property if one is not supplied explicitly in CREATE TABLE or CREATE STREAM statements.

If not set and no explicit value format is provided in the statement, via either the VALUE_FORMAT or the FORMAT property, the statement will be rejected as invalid.

For supported formats, see Serialization Formats.

`ksql.persistence.wrap.single.values`¶

Per query: no

Sets the default value for the WRAP_SINGLE_VALUE property if one is not supplied explicitly in CREATE TABLE, CREATE STREAM, CREATE TABLE AS SELECT or CREATE STREAM AS SELECT statements.

If not set and no explicit value is provided in the statement, the value format's default wrapping is used.

When set to true, ksqlDB serializes the column value nested within a JSON object, Avro record, or Protobuf message, depending on the format in use. When set to false, ksqlDB persists the column value without any nesting, as an anonymous value.

For example, consider the statement:

CREATE STREAM y AS SELECT f0 FROM x EMIT CHANGES;

The statement selects a single field as the value of stream y. If f0 has the integer value 10, with ksql.persistence.wrap.single.values set to true, the JSON format persists the value within a JSON object, as it would if the value had more fields:

{
   "F0": 10
}

With ksql.persistence.wrap.single.values set to false, the JSON format persists the single field's value as a JSON number: 10.

The properties control whether or not the field's value is written as a named field within a record or as an anonymous value.

This setting can be toggled using the SET command

SET 'ksql.persistence.wrap.single.values'='false';

For more information, refer to the CREATE TABLE, CREATE STREAM, CREATE TABLE AS SELECT or CREATE STREAM AS SELECT statements.

Note

Not all formats support wrapping and unwrapping. If you use a format that doesn't support the default value you set, the format ignores the setting. For information on which formats support wrapping and unwrapping, see the serialization docs.

`ksql.properties.overrides.denylist`¶

Per query: no

Specifies the server properties that ksqlDB clients and users can't override.

Important

Validation of a dynamic property assignment doesn't happen until a DDL or query statement executes, so an attempt to set a property that's on the deny list doesn't cause an immediate error.

For example, the following commands show an attempt to set the ksql.streams.num.stream.threads property, which is on the deny list. The override error doesn't appear until the show streams command executes. The unset command removes the error.

ksql> set 'ksql.streams.num.stream.threads'='4';
Successfully changed local property 'ksql.streams.num.stream.threads' from '4' to '4'.

ksql> show streams;
Cannot override property 'ksql.streams.num.stream.threads'

ksql> unset 'ksql.streams.num.stream.threads';
Successfully unset local property 'ksql.streams.num.stream.threads' (value was '4').

ksql> show streams;

  Stream Name         | Kafka Topic                 | Format 
------------------------------------------------------------
  KSQL_PROCESSING_LOG | default_ksql_processing_log | JSON   
------------------------------------------------------------

`ksql.schema.registry.url`¶

Per query: no

The Schema Registry URL path to connect ksqlDB to. To communicate with Schema Registry over a secure connection, see Configure ksqlDB for Secured Confluent Schema Registry.

`ksql.service.id`¶

Per query: no

The service ID of the ksqlDB server. This is used to define the ksqlDB cluster membership of a ksqlDB Server instance.

If multiple ksqlDB servers connect to the same Kafka cluster (i.e. the same bootstrap.servers and the same ksql.service.id) they form a ksqlDB cluster and share the workload.

If multiple ksqlDB servers connect to the same Kafka cluster but don't have the same ksql.service.id, they each get a different command topic and form separate ksqlDB clusters, by ksql.service.id.

By default, the service ID of ksqlDB servers is default_. The service ID is also used as the prefix for the internal topics created by ksqlDB. Using the default value ksql.service.id, the ksqlDB internal topics will be prefixed as _confluent-ksql-default_. For example, _command_topic becomes _confluent-ksql-default__command_topic).

Important

By convention, the ksql.service.id property should end with a separator character of some form, like a dash or underscore, as this makes the internal topic names easier to read.

`ksql.source.table.materialization.enabled`¶

Per query: no

Controls whether the SOURCE table feature is enabled. If you specify the SOURCE clause when you create a table, you can execute pull queries against the table. For more information, see SOURCE Tables.

`ksql.headers.columns.enabled`¶

Per query: no

Controls whether creating new streams/tables with HEADERS or HEADER('<key>') columns is allowed. If you specify a HEADERS or HEADER('<key>') column when you create a stream or table and ksql.headers.columns.enabled is set to false, then the statement is rejected. Existing sources with HEADERcolumns can be queried though.

`ksql.streams.auto.offset.reset`¶

Per query: yes

Determines what to do when there is no initial offset in Apache Kafka® or if the current offset doesn't exist on the server. The default value in ksqlDB is latest, which means all Kafka topics are read from the latest available offset. For example, to change it to earliest by using the ksqlDB CLI:

SET 'auto.offset.reset'='earliest';

For more information, see Kafka Consumer and AUTO_OFFSET_RESET_CONFIG.

`ksql.streams.bootstrap.servers`¶

Per query: no

A list of host and port pairs that is used for establishing the initial connection to the Kafka cluster. This list should be in the form host1:port1,host2:port2,... The default value in ksqlDB is localhost:9092. For example, to change it to 9095 by using the ksqlDB CLI:

SET 'bootstrap.servers'='localhost:9095';

For more information, see Streams parameter reference and BOOTSTRAP_SERVERS_CONFIG.

`ksql.streams.buffered.records.per.partition`¶

Per query: yes

The maximum number of records to buffer per partition. The default is 1000.

`ksql.streams.cache.max.bytes.buffering`¶

The maximum number of memory bytes to be used for buffering across all threads. The default value in ksqlDB is 10000000 (~ 10 MB). Here is an example to change the value to 20000000 by using the ksqlDB CLI:

SET 'cache.max.bytes.buffering'='20000000';

For more information, see the Streams parameter reference and CACHE_MAX_BYTES_BUFFERING_CONFIG.

`ksql.streams.commit.interval.ms`¶

Per query: no (may be set with ALTER SYSTEM, for Confluent Cloud only)

The frequency to save the position of the processor. The default value in ksqlDB is 2000. Here is an example to change the value to 5000 by using the ksqlDB CLI:

SET 'commit.interval.ms'='5000';

For more information, see the Streams parameter reference and COMMIT_INTERVAL_MS_CONFIG,

`ksql.streams.max.task.idle.ms`¶

Per query: yes

The maximum amount of time a task will idle without processing data when waiting for all of its input partition buffers to contain records. This can help avoid potential out-of-order processing when the task has multiple input streams, as in a join, for example.

Setting this to a nonzero value may increase latency but will improve time synchronization.

For more information, see max.task.idle.ms.

`ksql.streams.num.standby.replicas`¶

Per query: no (may be set with ALTER SYSTEM, for Confluent Cloud only)

Sets the number of hot-standby replicas of internal state to maintain. If a server fails and a standby replica is present, the standby will be able to take over active processing immediately for any of the failed server's tasks.

Additionally, if High Availability is enabled, and a server is offline, pull queries for its tasks can fail over to the standby replicas.

Configuring standbys enables you to minimize the recovery time for both stream processing and pull queries in the event of a failure. Regardless of the configuration value, ksqlDB can provision only one replica on each server, so you need at least two servers in the cluster to provision an active replica and a standby replica, for example.

`ksql.streams.num.stream.threads`¶

Per query: no

This number of stream threads in an instance of the Kafka Streams application. The stream processing code runs in these threads. For more information about the Kafka Streams threading model, see Threading Model.

`ksql.streams.processing.guarantee`¶

Per query: no (may be set with ALTER SYSTEM, for Confluent Cloud only)

The processing semantics to use for persistent queries. The default is at_least_once. To enable exactly-once semantics, use exactly_once.

For more information, see Processing Guarantees.

`ksql.streams.producer.compression.type`¶

Per query: no (may be set with ALTER SYSTEM, for Confluent Cloud only)

The type of compression used by streams producers for topics created by INSERT INTO, CREATE TABLE AS SELECT, and CREATE STREAM AS SELECT statements. The default is snappy.

This setting is distinct from the ksql.compression.type config, which sets the compression type used by Kafka producers, like the INSERT VALUES statement.

`ksql.streams.state.dir`¶

Per query: no

Sets the storage directory for stateful operations, like aggregations and joins, to a durable location. By default, state is stored in the /tmp/kafka-streams directory.

Note

The state storage directory must be unique for every server running on the machine. Otherwise, servers may appear to be stuck and not doing any work.

`ksql.streams.task.timeout.ms`¶

Per query: yes

The maximum amount of time, in milliseconds, a task might stall due to internal errors and retries until an error is raised. For a timeout of 0ms, a task would raise an error for the first internal error. For any timeout larger than 0ms, a task will retry at least once before an error is raised. The default is 300000 (5 minutes).

`ksql.queries.file`¶

Per query: no

A file that specifies a predefined set of queries for the ksqlDB cluster. For an example, see Non-interactive (Headless) ksqlDB Usage.

`ksql.query.persistent.active.limit`¶

Per query: no

The maximum number of persistent queries that may be running at any given time. Applies to interactive mode only. Once the limit is reached, commands that try to start additional persistent queries will be rejected. Users may terminate existing queries before attempting to start new ones to avoid hitting the limit. The default is no limit.

When setting up ksqlDB servers, it may be desirable to configure this limit to prevent users from overloading the server with too many queries, since throughput suffers as more queries are run simultaneously, and also because there is some small CPU overhead associated with starting each new query. For more information, see Sizing Recommendations.

`ksql.query.pull.enable.standby.reads`¶

Per query: yes

Config to enable/disable forwarding pull queries to standby hosts when the active is dead. This means that stale values may be returned for these queries since standby hosts receive updates from the changelog topic (to which the active writes to) asynchronously. Turning on this configuration, effectively sacrifices consistency for higher availability.

Setting to true guarantees high availability for pull queries. If set to false, pull queries will fail when the active is dead and until a new active is elected. Default value is false.

For using this functionality, the server must be configured with ksql.streams.num.standby.replicas >= 1, so standbys are actually enabled for the underlying Kafka Streams topologies. We also recommend ksql.heartbeat.enable=true, to ensure pull queries quickly route around dead/failed servers, without wastefully attempting to open connections to it (which can be slow & resource in-efficient).

`ksql.query.pull.max.allowed.offset.lag`¶

Per query: yes

Config to control the maximum lag tolerated by a pull query against a table, expressed as the number of messages a given table-partition is behind, compared to the changelog topic. This is applied to all servers, both active and standbys included. This can be overridden per query, from the CLI (using SET command) or the pull query REST endpoint (by including it in the request e.g: "streamsProperties": {"ksql.query.pull.max.allowed.offset.lag": "100"}).

By default, any amount of lag is allowed. For using this functionality, the server must be configured with ksql.heartbeat.enable=true and ksql.lag.reporting.enable=true, so the servers can exchange lag information between themselves ahead of time, to validate pull queries against the allowed lag.

`ksql.query.pull.table.scan.enabled`¶

Per query: yes

Config to control whether table scans are permitted when executing pull queries. Without this enabled, only key lookups are used. Enabling table scans removes various restrictions on what types of queries are allowed. In particular, these pull query types are now permitted:

No WHERE clause
Range queries on keys
Equality and range queries on non-key columns
Multi-column key queries without specifying all key columns

There may be significant performance implications to using these types of queries, depending on the size of the data and other workloads running, so use this config carefully.

Also, note that this config can be set on the CLI, but only used to disable table scans:

SET 'ksql.query.pull.table.scan.enabled'='false';

The server will reject requests that attempt to enable table scans. Disabling table scans per request can be useful when throwing an error is preferable to doing the potentially expensive scan.

`ksql.query.pull.interpreter.enabled`¶

Per query: yes

Controls whether pull queries use the interpreter or the code compiler as their expression evaluator. The interpreter is the default. The code compiler is used for persistent and push queries, which are naturally longer-lived than pull queries. The overhead of compilation slows down pull queries significantly, so using an interpreter gives significant performance gains. This can be disabled per query if the code compiler is preferred.

`ksql.query.pull.max.qps`¶

Per query: no

Sets a rate limit for pull queries, in queries per second. This limit is enforced per host, not per cluster. After hitting the limit, the host will fail pull query requests until it determines that it's no longer at the limit.

`ksql.query.pull.max.concurrent.requests`¶

Per query: no

Sets the maximum number of concurrent pull queries. This limit is enforced per host, not per cluster. After hitting the limit, the host will fail pull query requests until it determines that it's no longer at the limit.

`ksql.suppress.enabled`¶

Per query: yes

Enable the EMIT FINAL output refinement in a SELECT statement to suppress intermediate results on a windowed aggregation. The default is true.

`ksql.idle.connection.timeout.seconds`¶

Per query: no

Sets the timeout for idle connections. A connection is idle if there is no data in either direction on that connection for the duration of the timeout. This configuration can be helpful if you are issuing push queries that only receive data infrequently from the server, as otherwise those connections will be severed when the timeout (default 10 minutes) is hit.

Decreasing this timeout enables closing connections more aggressively to save server resources. Increasing this timeout makes the server more tolerant of low-data volume use cases.

`ksql.variable.substitution.enable`¶

Per query: no

Enables variable substitution through DEFINE statements.

`listeners`¶

Per query: no

The listeners setting controls the REST API endpoint for the ksqlDB Server. For more info, see ksqlDB REST API Reference.

The default listeners is http://0.0.0.0:8088, which binds to all IPv4 interfaces. Set listeners to http://[::]:8088 to bind to all IPv6 interfaces. Update this to a specific interface to bind only to a single interface. For example:

# Bind to all IPv4 interfaces.
listeners=http://0.0.0.0:8088

# Bind to all IPv6 interfaces.
listeners=http://[::]:8088

# Bind only to localhost.
listeners=http://localhost:8088

# Bind to specific hostname or ip.
listeners=http://server1245:8088

You can configure ksqlDB Server to use HTTPS. For more information, see Configure ksqlDB for HTTPS.

`response.http.headers.config`¶

Per query: no

Use to select which HTTP headers are returned in the HTTP response for Confluent Platform components. Specify multiple values in a comma-separated string using the format [action][header name]:[header value] where [action] is one of the following: set, add, setDate, or addDate. You must use quotation marks around the header value when the header value contains commas, for example:

response.http.headers.config="add Cache-Control: no-cache, no-store, must-revalidate", add X-XSS-Protection: 1; mode=block, add Strict-Transport-Security: max-age=31536000; includeSubDomains, add X-Content-Type-Options: nosniff  

`ksql.sink.partitions` (Deprecated)¶

Per query: no

The default number of partitions for the topics created by ksqlDB. The default is four. This property has been deprecated. For more info see the WITH clause properties in CREATE STREAM AS SELECT and CREATE TABLE AS SELECT.

`ksql.sink.replicas` (Deprecated)¶

Per query: no

The default number of replicas for the topics created by ksqlDB. The default is one. This property has been deprecated. For more info see the WITH clause properties in CREATE STREAM AS SELECT and CREATE TABLE AS SELECT.

Last update: 2022-09-06

Server configuration¶

compression.type¶

ksql.advertised.listener¶

ksql.assert.schema.default.timeout.ms¶

ksql.assert.topic.default.timeout.ms¶

ksql.connect.url¶

ksql.connect.worker.config¶

ksql.extension.dir¶

ksql.fail.on.deserialization.error¶

ksql.fail.on.production.error¶

ksql.functions.<UDF Name>.<UDF Config>¶

ksql.functions.collect_list.limit¶

ksql.functions.collect_set.limit¶

ksql.endpoint.logging.log.queries¶

ksql.endpoint.logging.ignored.paths.regex¶

ksql.heartbeat.enable¶

ksql.heartbeat.send.interval.ms¶

ksql.heartbeat.check.interval.ms¶

ksql.heartbeat.window.ms¶

ksql.heartbeat.missed.threshold.ms¶

ksql.heartbeat.discover.interval.ms¶

ksql.heartbeat.thread.pool.size¶

ksql.internal.listener¶

ksql.internal.topic.replicas¶

ksql.lag.reporting.enable¶

ksql.logging.processing.topic.auto.create¶

ksql.logging.processing.topic.name¶

ksql.logging.processing.topic.partitions¶

ksql.logging.processing.topic.replication.factor¶

ksql.logging.processing.stream.auto.create¶

ksql.logging.processing.stream.name¶

ksql.logging.processing.rows.include¶

ksql.logging.server.rate.limited.response.codes¶

ksql.logging.server.rate.limited.request.paths¶

ksql.metrics.tags.custom¶

ksql.output.topic.name.prefix¶

ksql.persistence.default.format.key¶

ksql.persistence.default.format.value¶

ksql.persistence.wrap.single.values¶

ksql.properties.overrides.denylist¶

ksql.schema.registry.url¶

ksql.service.id¶

ksql.source.table.materialization.enabled¶

ksql.headers.columns.enabled¶

ksql.streams.auto.offset.reset¶

ksql.streams.bootstrap.servers¶

ksql.streams.buffered.records.per.partition¶

ksql.streams.cache.max.bytes.buffering¶

ksql.streams.commit.interval.ms¶

ksql.streams.max.task.idle.ms¶

ksql.streams.num.standby.replicas¶

ksql.streams.num.stream.threads¶

ksql.streams.processing.guarantee¶

ksql.streams.producer.compression.type¶

ksql.streams.state.dir¶

ksql.streams.task.timeout.ms¶

ksql.queries.file¶

ksql.query.persistent.active.limit¶

ksql.query.pull.enable.standby.reads¶

ksql.query.pull.max.allowed.offset.lag¶

ksql.query.pull.table.scan.enabled¶

ksql.query.pull.interpreter.enabled¶

ksql.query.pull.max.qps¶

ksql.query.pull.max.concurrent.requests¶

ksql.suppress.enabled¶

ksql.idle.connection.timeout.seconds¶

ksql.variable.substitution.enable¶

listeners¶

response.http.headers.config¶

ksql.sink.partitions (Deprecated)¶

ksql.sink.replicas (Deprecated)¶

`compression.type`¶

`ksql.advertised.listener`¶

`ksql.assert.schema.default.timeout.ms`¶

`ksql.assert.topic.default.timeout.ms`¶

`ksql.connect.url`¶

`ksql.connect.worker.config`¶

`ksql.extension.dir`¶

`ksql.fail.on.deserialization.error`¶

`ksql.fail.on.production.error`¶

`ksql.functions.<UDF Name>.<UDF Config>`¶

`ksql.functions.collect_list.limit`¶

`ksql.functions.collect_set.limit`¶

`ksql.endpoint.logging.log.queries`¶

`ksql.endpoint.logging.ignored.paths.regex`¶

`ksql.heartbeat.enable`¶

`ksql.heartbeat.send.interval.ms`¶

`ksql.heartbeat.check.interval.ms`¶

`ksql.heartbeat.window.ms`¶

`ksql.heartbeat.missed.threshold.ms`¶

`ksql.heartbeat.discover.interval.ms`¶

`ksql.heartbeat.thread.pool.size`¶

`ksql.internal.listener`¶

`ksql.internal.topic.replicas`¶

`ksql.lag.reporting.enable`¶

`ksql.logging.processing.topic.auto.create`¶

`ksql.logging.processing.topic.name`¶

`ksql.logging.processing.topic.partitions`¶

`ksql.logging.processing.topic.replication.factor`¶

`ksql.logging.processing.stream.auto.create`¶

`ksql.logging.processing.stream.name`¶

`ksql.logging.processing.rows.include`¶

`ksql.logging.server.rate.limited.response.codes`¶

`ksql.logging.server.rate.limited.request.paths`¶

`ksql.metrics.tags.custom`¶

`ksql.output.topic.name.prefix`¶

`ksql.persistence.default.format.key`¶

`ksql.persistence.default.format.value`¶

`ksql.persistence.wrap.single.values`¶

`ksql.properties.overrides.denylist`¶

`ksql.schema.registry.url`¶

`ksql.service.id`¶

`ksql.source.table.materialization.enabled`¶

`ksql.headers.columns.enabled`¶

`ksql.streams.auto.offset.reset`¶

`ksql.streams.bootstrap.servers`¶

`ksql.streams.buffered.records.per.partition`¶

`ksql.streams.cache.max.bytes.buffering`¶

`ksql.streams.commit.interval.ms`¶

`ksql.streams.max.task.idle.ms`¶

`ksql.streams.num.standby.replicas`¶

`ksql.streams.num.stream.threads`¶

`ksql.streams.processing.guarantee`¶

`ksql.streams.producer.compression.type`¶

`ksql.streams.state.dir`¶

`ksql.streams.task.timeout.ms`¶

`ksql.queries.file`¶

`ksql.query.persistent.active.limit`¶

`ksql.query.pull.enable.standby.reads`¶

`ksql.query.pull.max.allowed.offset.lag`¶

`ksql.query.pull.table.scan.enabled`¶

`ksql.query.pull.interpreter.enabled`¶

`ksql.query.pull.max.qps`¶

`ksql.query.pull.max.concurrent.requests`¶

`ksql.suppress.enabled`¶

`ksql.idle.connection.timeout.seconds`¶

`ksql.variable.substitution.enable`¶

`listeners`¶

`response.http.headers.config`¶

`ksql.sink.partitions` (Deprecated)¶

`ksql.sink.replicas` (Deprecated)¶