Configuration Properties
The following application properties are supported by the Spring Boot auto-configuration.
| Name | Description | Default |
|---|---|---|
|
Authentication parameter(s) as a map of parameter names to parameter values. |
|
|
Fully qualified class name of the authentication plugin. |
|
|
Duration to wait for a connection to server to be established. |
|
|
Server response read time out for any request. |
|
|
Server request time out for any request. |
|
|
Pulsar web URL for the admin endpoint in the format '(http|https)://host:port'. |
|
|
Authentication parameter(s) as a map of parameter names to parameter values. |
|
|
Fully qualified class name of the authentication plugin. |
|
|
Duration to wait for a connection to a broker to be established. |
|
|
List of backup clusters. The backup cluster is chosen in the sequence of the given list. If all backup clusters are available, the Pulsar client chooses the first backup cluster. |
|
|
Frequency of performing a probe task. |
|
|
Delay before the Pulsar client switches from the primary cluster to the backup cluster. |
|
|
Cluster failover policy. |
|
|
Delay before the Pulsar client switches from the backup cluster to the primary cluster. |
|
|
Client lookup timeout. |
|
|
Client operation timeout. |
|
|
Pulsar service URL in the format '(pulsar|pulsar+ssl)://host:port'. |
|
|
Number of threads to be used for handling connections to brokers. |
|
|
Number of threads to be used for message listeners. |
|
|
Name of the dead topic where the failing messages will be sent. |
|
|
Name of the initial subscription of the dead letter topic. When not set, the initial subscription will not be created. However, when the property is set then the broker’s 'allowAutoSubscriptionCreation' must be enabled or the DLQ producer will fail. |
|
|
Maximum number of times that a message will be redelivered before being sent to the dead letter queue. |
|
|
Name of the retry topic where the failing messages will be sent. |
|
|
Consumer name to identify a particular consumer from the topic stats. |
|
|
Priority level for shared subscription consumers. |
|
|
Whether to read messages from the compacted topic rather than the full message backlog. |
|
|
Whether to auto retry messages. |
|
|
Position where to initialize a newly created subscription. |
|
|
Subscription mode to be used when subscribing to the topic. |
|
|
Subscription name for the consumer. |
|
|
Determines which type of topics (persistent, non-persistent, or all) the consumer should be subscribed to when using pattern subscriptions. |
|
|
Subscription type to be used when subscribing to a topic. |
|
|
Topics the consumer subscribes to. |
|
|
Pattern for topics the consumer subscribes to. |
|
|
Whether to enable default tenant and namespace support for topics. |
|
|
Default namespace to use when producing or consuming messages against a non-fully-qualified topic URL. |
|
|
Default tenant to use when producing or consuming messages against a non-fully-qualified topic URL. |
|
|
List of mappings from message type to topic name and schema info to use as a defaults when a topic name and/or schema is not explicitly specified when producing or consuming messages of the mapped type. |
|
|
Whether to enable function support. |
|
|
Whether to stop processing further function creates/updates when a failure occurs. |
|
|
Whether to throw an exception if any failure is encountered during server startup while creating/updating functions. |
|
|
Whether to throw an exception if any failure is encountered during server shutdown while enforcing stop policy on functions. |
|
|
Number of threads used by listener container. |
|
|
Whether to record observations for when the Observations API is available and the client supports it. |
|
|
SchemaType of the consumed messages. |
|
|
Type of access to the topic the producer requires. |
|
|
Whether to automatically batch messages. |
|
|
Whether to enable caching in the PulsarProducerFactory. |
|
|
Time period to expire unused entries in the cache. |
|
|
Initial size of cache. |
|
|
Maximum size of cache (entries). |
|
|
Whether to split large-size messages into multiple chunks. |
|
|
Message compression type. |
|
|
Message hashing scheme to choose the partition to which the message is published. |
|
|
Message routing mode for a partitioned producer. |
|
|
Name for the producer. If not assigned, a unique name is generated. |
|
|
Time before a message has to be acknowledged by the broker. |
|
|
Topic the producer will publish to. |
|
|
Reader name. |
|
|
Whether to read messages from a compacted topic rather than a full message backlog of a topic. |
|
|
Subscription name. |
|
|
Prefix of subscription role. |
|
|
Topics the reader subscribes to. |
|
|
Whether to record observations for when the Observations API is available. |
|
|
Whether transaction support is enabled. |
|