[
https://issues.apache.org/jira/browse/FLINK-17529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17104955#comment-17104955
]
Austin Cawley-Edwards edited comment on FLINK-17529 at 5/11/20, 11:01 PM:
--------------------------------------------------------------------------
After more investigation, I don't think we're able to replace this without
tackling the issues brought up in FLINK-10195. I think there are other ways of
flow-control than described in that ticket though, which might be worth
pursuing. Should I close this ticket and move the conversation back to
FLINK-10195? Sorry for creating it before diving in!
was (Author: austince):
After more investigation, I don't think we're able to replace this without
tackling the issues brought up in FLINK-10195. I think there are other ways of
flow-control than described in that ticket though, which might be worth
pursuing. Should I close this ticket and move the conversation back to
FLINK-10195?
> Replace Deprecated RMQ QueueingConsumer
> ---------------------------------------
>
> Key: FLINK-17529
> URL: https://issues.apache.org/jira/browse/FLINK-17529
> Project: Flink
> Issue Type: Improvement
> Components: Connectors/ RabbitMQ
> Affects Versions: 1.10.0
> Reporter: Austin Cawley-Edwards
> Priority: Minor
>
> The RMQ QueueingConsumer is used in the RMQSource to get a simple blocking
> consumer. This has been deprecated in `com.rabbitmq:amqp-client` 4.2.0 and is
> removed in 5.x. It should be replaced by a
> `com.rabbitmq.client.DefaultConsumer`.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
