camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CAMEL-11193) Route from kafka topic to another kafka topic issue
Date Mon, 24 Apr 2017 11:36:04 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-11193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen resolved CAMEL-11193.
---------------------------------
    Resolution: Fixed

> 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
>            Assignee: Claus Ibsen
>             Fix For: 2.19.0
>
>
> 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)

Mime
View raw message