[
https://issues.apache.org/jira/browse/CAMEL-16060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17306024#comment-17306024
]
Omar Al-Safi edited comment on CAMEL-16060 at 3/22/21, 8:59 AM:
----------------------------------------------------------------
for your info, [camel-vertx-kafka
|https://camel.apache.org/components/latest/vertx-kafka-component.html#_message_headers_evaluated_by_the_component_producer],
uses only one message key. As we know, message key can be as well partition
key and thus made no sense to keep two keys headers which may lead to confusion.
was (Author: omarsmak):
for your info, [camel-vertx-kafka
|https://camel.apache.org/components/latest/vertx-kafka-component.html], uses
only message key. As we know, message key can be as well partition key and thus
made no sense to keep two keys headers which may lead to confusion.
> camel-kafka - decouple kafka.PARTITION_KEY from kafka.KEY
> ---------------------------------------------------------
>
> Key: CAMEL-16060
> URL: https://issues.apache.org/jira/browse/CAMEL-16060
> Project: Camel
> Issue Type: Improvement
> Components: camel-kafka
> Affects Versions: 3.7.0, 2.25.3
> Reporter: Jens Kordowski
> Priority: Major
> Fix For: 3.10.0
>
>
> Currently, the camel-kafka producer requires the definition of
> kafka.PARTITION_KEY *and* kafka.KEY to specify the partition to send to.
> While the key is usually used to determine the partition to send to, I don't
> understand the hard limitation on this header, when specifically defining the
> exact partition to send to anyway (via kafka.PARTITION_KEY).
> Also, this is not clearly stated in the documentation.
> Not sure, if this qualifies as bug or improvement, looks like a limitation to
> me. I can create a PR, if desired.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
