[
https://issues.apache.org/jira/browse/FLINK-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15322345#comment-15322345
]
Robert Metzger edited comment on FLINK-3763 at 6/9/16 10:52 AM:
----------------------------------------------------------------
The Javadoc of the close() method (we are calling) states that its sending a
success message:
{quote}
Close this connection and all its channels with the \{@link
com.rabbitmq.client.AMQP#REPLY_SUCCESS} close code and message 'OK'.
{quote}
So I guess that is okay?
was (Author: rmetzger):
The Javadoc of the close() method (we are calling) states that its sending a
success message:
{quote}
Close this connection and all its channels
with the {@link com.rabbitmq.client.AMQP#REPLY_SUCCESS} close code
and message 'OK'.
{quote}
> 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)
