[ 
https://issues.apache.org/jira/browse/FLINK-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15308512#comment-15308512
 ] 

ASF GitHub Bot commented on FLINK-3763:
---------------------------------------

Github user rmetzger commented on a diff in the pull request:

    https://github.com/apache/flink/pull/2054#discussion_r65253016
  
    --- Diff: docs/apis/streaming/connectors/rabbitmq.md ---
    @@ -71,23 +71,25 @@ Example:
     <div class="codetabs" markdown="1">
     <div data-lang="java" markdown="1">
     {% highlight java %}
    +RMQConnectionConfig connectionConfig = new 
RMQConnectionConfig.Builder().build();
    --- End diff --
    
    As I've written below, I would prefer if users would not rely on the fact 
that "localhost" is the default value here.
    Once the builder has been changed, we would expect the user to call 
`.setHost("localhost")` here.


> RabbitMQ Source/Sink standardize connection parameters
> ------------------------------------------------------
>
>                 Key: FLINK-3763
>                 URL: https://issues.apache.org/jira/browse/FLINK-3763
>             Project: Flink
>          Issue Type: Improvement
>          Components: Streaming Connectors
>    Affects Versions: 1.0.1
>            Reporter: Robert Batts
>            Assignee: Subhankar Biswas
>
> The RabbitMQ source and sink should have the same capabilities in terms of 
> establishing a connection, currently the sink is lacking connection 
> parameters that are available on the source. Additionally, VirtualHost should 
> be an offered parameter for multi-tenant RabbitMQ clusters (if not specified 
> it goes to the vhost '/').
> Connection Parameters
> ===================
> - Host - Offered on both
> - Port - Source only
> - Virtual Host - Neither
> - User - Source only
> - Password - Source only
> Additionally, it might be worth offer the URI as a valid constructor because 
> that would offer all 5 of the above parameters in a single String.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to