Beatriz Aparecida de Freitas Rodrigues created KAFKA-18171:
--------------------------------------------------------------
Summary: Unexpected Change in bootstrap.servers Behavior After
Upgrade to 3.8.0
Key: KAFKA-18171
URL: https://issues.apache.org/jira/browse/KAFKA-18171
Project: Kafka
Issue Type: Bug
Components: config
Affects Versions: 3.8.0
Environment: Operating system: windows 11
Kafka Version: 3.8.0
Previous Version: 3.7.0
Configuration:
- `bootstrap.servers: "140.2.15.25:9092 140.2.15.26:9092 140.2.15.27:9092"`
Reporter: Beatriz Aparecida de Freitas Rodrigues
After upgrading from Kafka version *3.7.0* to 3.8.0, I encountered an issue
with the configuration of the `bootstrap.servers` property.
In previous versions, it was possible to configure the `bootstrap.servers` with
space-separated URLs, like this:
{code:java}
bootstrap.servers: "140.2.15.25:9092 140.2.15.26:9092 140.2.15.27:9092"
{code}
However, with version {*}3.8.0{*}, this configuration results in the following
exception:
{code:java}
org.apache.kafka.common.config.ConfigException: Invalid url in
bootstrap.servers: 140.2.15.25:9092 140.2.15.26:9092 140.2.15.27:9092 {code}
The configuration only works correctly if the URLs are separated by commas, as
shown below:
{code:java}
bootstrap.servers: "140.2.15.25:9092,140.2.15.26:9092,140.2.15.27:9092" {code}
This behavior appears to be a change from previous versions where
space-separated URLs were accepted.
*Reproducible Example:*
To demonstrate the issue, I created a minimal project that reproduces the
problem. You can find it here:
[GitHub Repository|https://github.com/BeatrizRodrigues/kafka-config-test]
*Question:*
Is this the expected behavior for version *3.8.0* ? Was support for
space-separated `bootstrap.servers` values intentionally deprecated, or is this
a bug introduced in the latest release?
Looking forward to clarification on whether this is an intentional change or a
bug. Thank you!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
