- Notifications
You must be signed in to change notification settings - Fork 41.5k
Spring Boot 3.2.0 M3 Configuration Changelog
Configuration property changes between 3.2.0-M2
and 3.2.0-M3
Key | Replacement | Reason |
---|---|---|
| ||
| ||
| ||
| ||
| ||
| ||
| ||
|
Key | Default value | Description |
---|---|---|
|
| Whether to export meter metadata (unit and description) to the Dynatrace backend. |
| ||
|
| Whether schema should be compared to the application to detect missing mappings. |
| 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 or 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. |
|
| Client lookup timeout. |
|
| Client operation timeout. |
|
| Pulsar service URL in the format '(pulsar or pulsar+ssl)://host:port'. |
| Name of the dead topic where the failing messages will be sent. | |
| Name of the initial subscription of the dead letter topic. | |
|
| 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. | |
| 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. |
|
| 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. | |
|
| 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. | |
| Topis the reader subscribes to. | |
|
| Whether to record observations for when the Observations API is available. |
| Virtual host of a RabbitMQ instance with the Stream plugin enabled. | |
|
| Whether to resolve the multipart request strictly comply with the Servlet specification, only to be used for "multipart/form-data" requests. |