[
https://issues.apache.org/jira/browse/FLINK-7267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17108575#comment-17108575
]
Austin Cawley-Edwards edited comment on FLINK-7267 at 5/15/20, 7:05 PM:
------------------------------------------------------------------------
I put in a PR for option A, as it's less change – if we find that many people
are overriding the connection, maybe that would be a good time to add it to the
connection config builder? Anyways, can you assign this ticket to me (oops)?
Thanks!
was (Author: austince):
I put in a PR for option A, as it's less change -- if we find that many people
are overriding the connection, maybe that would be a good time to add it to the
connection config builder? Anyways, can you assign this ticket to me? Thanks!
> Add support for lists of hosts to connect
> -----------------------------------------
>
> Key: FLINK-7267
> URL: https://issues.apache.org/jira/browse/FLINK-7267
> Project: Flink
> Issue Type: Improvement
> Components: Connectors/ RabbitMQ
> Affects Versions: 1.3.0
> Reporter: Hu Hailin
> Priority: Minor
> Labels: pull-request-available
>
> The RMQConnectionConfig can assign one host:port only. I want to connect to a
> cluster with an available node.
> My workaround is write my own sink extending RMQSink and override open(),
> assigning the nodes list in it.
> {code:java}
> connection = factory.newConnection(addrs)
> {code}
> I still need to build the RMQConnectionConfig with a dummy host:port or a
> node in list. It's annoying.
> I think it is better to provide a configuration for it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
