You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@qpid.apache.org by "Robbie Gemmell (Jira)" <ji...@apache.org> on 2020/09/23 10:12:00 UTC

[jira] [Updated] (QPID-8467) [AMQP 1.0] annotations added by broker use string keys rather than symbols, mutates existing symbol keys

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

Robbie Gemmell updated QPID-8467:
---------------------------------
    Summary: [AMQP 1.0] annotations added by broker use string keys rather than symbols, mutates existing symbol keys  (was: [AMQP 1.0] annotations added by broker are sent with string keys rather than symbols)

> [AMQP 1.0] annotations added by broker use string keys rather than symbols, mutates existing symbol keys
> --------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-8467
>                 URL: https://issues.apache.org/jira/browse/QPID-8467
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Broker
>    Affects Versions: qpid-cpp-1.39.0
>            Reporter: Gordon Sim
>            Priority: Major
>
> Noticed while trying out QPID-5285, the broker adds an illegal string typed annotation key for the added timestamp.
> Worse, the addition also causes the broker to mutate incoming symbol-keyed annotations to also use illegal string keys as well. As a result, even if a recipient could ignore the wayward type (which many cant) for any added annotations it wasn't specifically aware of, it would still find any annotations it was aware of to be broken.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org