[
https://issues.apache.org/jira/browse/QPID-7606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7606:
-----------------------------
Description:
Queues and exchanges should have something akin to an "alternate binding"
rather than an alternate exchange. From this we can simplify the DLQ
implementation to remove the need for DLEs (or at worst have a single DLE).
Alternate Bindings could be modelled as {{\{destination, arguments\}}}. A
supported argument might be {{replacementRoutingKey}} which if set could direct
the routing through the alternate(s) (This is separate - see QPID-7771).
This work includes:
* changes to the model object themselves and the routing algorithms
* update the configuration upgrades to remap Exchange#alternativeExchange and
Queue#alternativeExchange into the new model.
* the facility for automatic creation of a DLQ should be retained but it can be
simplified to not create an DLE exchange.
* On upgrade, existing users' DLQ/DLEs must be retained as is, that is, there
is no requirement to eliminate existing DLEs. This is because we have no way
to predict if the users made additional changes to these objects.
was:
Queues and exchanges should have something akin to an "alternate binding"
rather than an alternate exchange. From this we can simplify the DLQ
implementation to remove the need for DLEs (or at worst have a single DLE).
Alternate Bindings could be modelled as {{\{destination, arguments\}}}. A
supported argument might be {{replacementRoutingKey}} which if set could direct
the routing through the alternate(s).
> Generalise Queue|Exchange#alternateExchange as alternateBinding
> ---------------------------------------------------------------
>
> Key: QPID-7606
> URL: https://issues.apache.org/jira/browse/QPID-7606
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
> Fix For: qpid-java-broker-7.0.0
>
>
> Queues and exchanges should have something akin to an "alternate binding"
> rather than an alternate exchange. From this we can simplify the DLQ
> implementation to remove the need for DLEs (or at worst have a single DLE).
> Alternate Bindings could be modelled as {{\{destination, arguments\}}}. A
> supported argument might be {{replacementRoutingKey}} which if set could
> direct the routing through the alternate(s) (This is separate - see
> QPID-7771).
> This work includes:
> * changes to the model object themselves and the routing algorithms
> * update the configuration upgrades to remap Exchange#alternativeExchange and
> Queue#alternativeExchange into the new model.
> * the facility for automatic creation of a DLQ should be retained but it can
> be simplified to not create an DLE exchange.
> * On upgrade, existing users' DLQ/DLEs must be retained as is, that is, there
> is no requirement to eliminate existing DLEs. This is because we have no way
> to predict if the users made additional changes to these objects.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
