GitHub user theomega opened a pull request:

    https://github.com/apache/flink/pull/2073

    [FLINK-4025] Add possiblity for the RMQ Streaming Source to customize the 
queue

    This patch adds the possibilty for the user of the RabbitMQ
    Streaming Connector to customize the queue which is used. There
    are use-cases in which you want to set custom parameters for the
    queue (i.e. TTL of the messages if Flink reboots) or the
    possibility to bind the queue to an exchange afterwards.
    
    The commit doesn't change the actual behaviour but makes it
    possible for users to override the newly create `setupQueue`
    method and cutomize their implementation. This was not possible
    before.

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

    $ git pull https://github.com/theomega/flink 
rmq-streaming-connector_customize-queue

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

    https://github.com/apache/flink/pull/2073.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 #2073
    
----
commit 811e88f17f8469f7d01a69158ab7c062325eeb34
Author: Dominik Bruhn <domi...@relayr.io>
Date:   2016-06-05T21:18:56Z

    RMQ Streaming: Possibility to customize queue
    
    This patch adds the possibilty for th user of the RabbitMQ
    Streaming Connector to customize the queue which is used. There
    are use-cases in which you want to set custom parameters for the
    queue (i.e. TTL of the messages if Flink reboots) or the
    possibility to bind the queue to an exchange afterwards.
    
    The commit doesn't change the actual behaviour but makes it
    possible for users to override the newly create `setupQueue`
    method and cutomize their implementation. This was not possible
    before.

----


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to