[ 
https://issues.apache.org/jira/browse/QPID-5689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keith Wall resolved QPID-5689.
------------------------------
    Resolution: Not a Problem

QueueFactory contains a heuristic to determine the queue's type from its 
properties, in the case where type is absent.

> BDB Upgraders: Upgraded queues might not carry a top-level type attribute
> -------------------------------------------------------------------------
>
>                 Key: QPID-5689
>                 URL: https://issues.apache.org/jira/browse/QPID-5689
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: 0.26, 0.28, 0.29
>            Reporter: Keith Wall
>
> From 0.26 onwards, Qpid began to storing a queue type attribute within the 
> queue's attribute map. 
> For example, a priority queue (created from REST) is stored in the BDB store:
> {code:javascript}
> {"priorities":9,
>  "exclusive":false,
>  "name":"mynewqueue",
>  "owner":null,
>  "type":"priority"}
> {code}
> However, queues that have come the BDB upgrade route from early store 
> versions don't carry a type.  This is the JSON for the priority queue auto 
> upgraded by the BDB store upgraders from the test store "bdbstore-v5" by 0.26.
> {code:javascript}
> {
> "priorities":10,
> "arguments":{"x-qpid-priorities":10},
> "exclusive":false,
> "name":"myPriorityQueue",
> "owner":null}
> }
> {code}
> I'm not aware of this causing an issue for users of current versions (as 
> AMQQueueFactory currently infers queue type from the queue's arguments rather 
> than using type), but there is the potential for this inconsistency to cause 
> defects in the future should this inference ever be refactored.
> The *configuration store upgrader* should be enhanced to detect queues with 
> missing types and infer the type from the queue arguments.  This will remove 
> the inconsistency.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to