David Oftedal created CAMEL-16438:
-------------------------------------
Summary: Kafka component properties randomly end up under
camel.component.kafka or camel.component.configuration
Key: CAMEL-16438
URL: https://issues.apache.org/jira/browse/CAMEL-16438
Project: Camel
Issue Type: Bug
Components: camel-kafka
Affects Versions: 3.8.0
Reporter: David Oftedal
According to
[https://camel.apache.org/manual/latest/camel-3x-upgrade-guide-3_2.html#_configuring_components_via_spring_boot_auto_configuration]
, Camel component configuration should as of version 3.2 no longer use the
.configuration prefix.
In version 3.8, many properties have indeed moved out of .config. But some
properties are still only set if set with the .configuration prefix. As far as
I can tell, this non-exhaustive list contains valid examples:
* camel.component.kafka.configuration.brokers (specifically mentioned in the
documentation as having moved)
* camel.component.kafka.configuration.max-poll-records
* camel.component.kafka.configuration.group-id
* camel.component.kafka.configuration.topic
* camel.component.kafka.configuration.ssl-keystore-password
* camel.component.kafka.configuration.ssl-truststore-password
* camel.component.kafka.configuration.value-deserializer
Some properties seem to have moved *to* .configuration:
* camel.component.kafka.configuration.allow-manual-commit
* camel.component.kafka.configuration.break-on-first-error
Some related properties now appear to be split between two prefixes:
* camel.component.kafka.ssl-keystore-location and
camel.component.kafka.configuration.ssl-keystore-password
* camel.component.kafka.ssl-truststore-location and
camel.component.kafka.configuration.ssl-truststore-password
* camel.component.kafka.value-serializer and
camel.component.kafka.configuration.value-deserializer
Trying to figure out what goes where requires a pretty exhaustive and
error-prone search.
Obviously it's possible to copy and paste each property so that it's set both
with and without .configuration, but if the intent is to remove .configuration
altogether, would it be possible to either confirm or negate what we're seeing?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
