Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
From: williamd1618 <git@git.apache.org>
To: dev@camel.apache.org
Reply-To: dev@camel.apache.org
References: <git-pr-597-camel@git.apache.org>
In-Reply-To: <git-pr-597-camel@git.apache.org>
Subject: [GitHub] camel pull request: Fix KafkaProducer URI
Content-Type: text/plain
Message-Id: <20150901203440.1C266DFBBB@git1-us-west.apache.org>
Date: Tue,  1 Sep 2015 20:34:40 +0000 (UTC)

GitHub user williamd1618 reopened a pull request:

    https://github.com/apache/camel/pull/597

    Fix KafkaProducer URI

    Guarantees that if the KafkaEndpoint has a UriParam
    of topic the KeyedMessage will be sent to that topic,
    if it does not have a topic and the Exchange message
    has a header of kafka.TOPIC to use that instead.
    
    If executing an operation similar to:
    
    ```
    from("kafka:localhost:9092?topic=A&groupId=B....").to("kafka:localhost:9092?topic=B.....")
    ```
    
    The target topic is currently ignored in favor of topic A

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/williamd1618/camel camel-2.15.x

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/597.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #597
    
----
commit e6403b54ff705bf5912fc1df837b01f9fc230f48
Author: Daniel Williams <daniel.williams@pearson.com>
Date:   2015-08-21T20:39:18Z

    Fix KafkaProducer URI
    
    Guarantees that if the KafkaEndpoint has a UriParam
    of topic the KeyedMessage will be sent to that topic,
    if it does not have a topic and the Exchange message
    has a header of kafka.TOPIC to use that instead.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---