You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2022/02/07 10:44:01 UTC
[jira] [Updated] (FLINK-4043) Generalize RabbitMQ connector into AMQP connector
[ https://issues.apache.org/jira/browse/FLINK-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-4043:
----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was: auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Minor, please raise the priority and ask a committer to assign you the issue or revive the public discussion.
> Generalize RabbitMQ connector into AMQP connector
> -------------------------------------------------
>
> Key: FLINK-4043
> URL: https://issues.apache.org/jira/browse/FLINK-4043
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Common
> Reporter: Robert Metzger
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> Our current RabbitMQ connector is actually using a AMQP client implemented by RabbitMQ.
> AMQP is a protocol for message queues, implemented by different clients and brokers.
> I'm suggesting to rename the connector so that its more obvious to users of other brokers that they can use the connector as well.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)