[
https://issues.apache.org/jira/browse/FLINK-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-3769:
----------------------------------
Labels: auto-deprioritized-major auto-unassigned rabbitmq stale-minor
(was: auto-deprioritized-major auto-unassigned rabbitmq)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> RabbitMQ Sink ability to publish to a different exchange
> --------------------------------------------------------
>
> Key: FLINK-3769
> URL: https://issues.apache.org/jira/browse/FLINK-3769
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Common
> Affects Versions: 1.0.1
> Reporter: Robert Batts
> Priority: Minor
> Labels: auto-deprioritized-major, auto-unassigned, rabbitmq,
> stale-minor
>
> The RabbitMQ Sink can currently only publish to the "default" exchange. This
> exchange is a direct exchange, so the routing key will route directly to the
> queue name. Because of this, the current sink will only be 1-to-1-to-1 (1 job
> to 1 exchange which routes to 1 queue). Additionally, I believe that if a
> user decides to use a different exchange I think the following can be assumed:
> 1.) The provided exchange exists
> 2.) The user has declared the appropriate mapping and the appropriate queues
> exist in RabbitMQ (therefore, nothing needs to be created)
> RabbitMQ currently provides four types of exchanges. Three of these will be
> covered by just enabling exchanges (Direct, Fanout, Topic) because they use
> the routingkey (or nothing).
> The fourth exchange type relies on the message headers, which are currently
> set to null by default on the publish. These headers may be on a per message
> level, so the input of this stream will need to take this as input as well.
> This forth exchange could very well be outside of the scope of this
> Improvement and a "RabbitMQ Sink enable headers" Improvement might be the
> better way to go with this.
> Exchange Types: https://www.rabbitmq.com/tutorials/amqp-concepts.html
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
