You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Jean-Baptiste Onofré (Jira)" <ji...@apache.org> on 2019/11/01 05:13:00 UTC
[jira] [Updated] (BEAM-8513) RabbitMqIO: Allow reads from
exchange-bound queue without declaring the exchange
[ https://issues.apache.org/jira/browse/BEAM-8513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated BEAM-8513:
---------------------------------------
Status: Open (was: Triage Needed)
> RabbitMqIO: Allow reads from exchange-bound queue without declaring the exchange
> --------------------------------------------------------------------------------
>
> Key: BEAM-8513
> URL: https://issues.apache.org/jira/browse/BEAM-8513
> Project: Beam
> Issue Type: Improvement
> Components: io-java-rabbitmq
> Environment: testing with DirectRunner
> Reporter: Nick Aldwin
> Assignee: Jean-Baptiste Onofré
> Priority: Critical
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> The RabbitMqIO always declares an exchange if it is configured to read from it. This is problematic with pre-existing exchanges (a relatively common pattern), as there's no provided configuration for the exchange beyond exchange type. (We stumbled on this because RabbitMqIO always declares a non-durable exchange, which fails if the exchange already exists as a durable exchange)
>
> A solution to this would be to allow RabbitMqIO to read from an exchange without declaring it. This pattern is already available for queues via the `queueDeclare` flag. I propose an `exchangeDeclare` flag which preserves existing behavior except for skipping the call to `exchangeDeclare` before binding the queue to the exchange.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)