You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2017/04/24 10:35:04 UTC
[jira] [Commented] (CAMEL-11193) Route from kafka topic to another
kafka topic issue
[ https://issues.apache.org/jira/browse/CAMEL-11193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980980#comment-15980980 ]
Claus Ibsen commented on CAMEL-11193:
-------------------------------------
You can turn on the bridgeEndpoint option for this
{code}
to("kafka:bar?bridgeEndpoint=true")
{code}
> Route from kafka topic to another kafka topic issue
> ---------------------------------------------------
>
> Key: CAMEL-11193
> URL: https://issues.apache.org/jira/browse/CAMEL-11193
> Project: Camel
> Issue Type: Improvement
> Components: camel-kafka
> Affects Versions: 2.19.0
> Reporter: Claus Ibsen
>
> Because the consumer set headers with kafka topic and partition from the consumer, then these will override the endpoint configured on the producer, eg
> {code}
> from("kafka:foo")
> ..
> to("kafka:bar")
> {code}
> will end up going back to foo.
> You can remove the headers to make it work
> {code}
> from("kafka:foo")
> ..
> removeHeaders("kafka*")
> to("kafka:bar")
> {code}
> But maybe we should have an option on the producer that takes the endpoint value always, and you need to turn the option on to allow header overrides.
> Another option is to detect that its the same topic to avoid sending it back to itself.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)