[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

[jira] [Commented] (QPID-8467) [AMQP 1.0] annotations added by broker are sent with string keys rather than symbols

[ https://issues.apache.org/jira/browse/QPID-8467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17200703#comment-17200703 ] Robbie Gemmell commented on QPID-8467: -- Updated details along lines of my duplicate QPID-8468 >

[jira] [Updated] (QPID-8467) [AMQP 1.0] annotations added by broker are sent with string keys rather than symbols

[ https://issues.apache.org/jira/browse/QPID-8467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-8467: - Affects Version/s: qpid-cpp-1.39.0 Description: Noticed while trying out QPID-5285, the

[jira] [Closed] (QPID-8468) [cpp] broker adds illegal string keyed annotations, mutates incoming symbol keys when doing so

[ https://issues.apache.org/jira/browse/QPID-8468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell closed QPID-8468. Resolution: Duplicate Duplicates QPID-8467 > [cpp] broker adds illegal string keyed annotations,

[jira] [Created] (QPID-8468) [cpp] broker adds illegal string keyed annotations, mutates incoming symbol keys when doing so

Robbie Gemmell created QPID-8468: Summary: [cpp] broker adds illegal string keyed annotations, mutates incoming symbol keys when doing so Key: QPID-8468 URL: https://issues.apache.org/jira/browse/QPID-8468

[jira] [Created] (QPID-8467) [AMQP 1.0] annotations added by broker are sent with string keys rather than symbols

Gordon Sim created QPID-8467: Summary: [AMQP 1.0] annotations added by broker are sent with string keys rather than symbols Key: QPID-8467 URL: https://issues.apache.org/jira/browse/QPID-8467 Project:

[jira] [Commented] (QPID-5285) [AMQP 1.0] timestamped messages not supported

[ https://issues.apache.org/jira/browse/QPID-5285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17200695#comment-17200695 ] ASF GitHub Bot commented on QPID-5285: -- gemmellr commented on pull request #20: URL:

[GitHub] [qpid-cpp] gemmellr commented on pull request #20: QPID-5285 [AMQP 1.0] timestamped messages not supported

gemmellr commented on pull request #20: URL: https://github.com/apache/qpid-cpp/pull/20#issuecomment-697256106 Or, as @grs noted in discussion, its instead likely just that there is a general existing issue with handling adding annotations, which this change falls foul of simply by doing

[GitHub] [qpid-cpp] gemmellr commented on pull request #20: QPID-5285 [AMQP 1.0] timestamped messages not supported

gemmellr commented on pull request #20: URL: https://github.com/apache/qpid-cpp/pull/20#issuecomment-697239730 This change results in the broker using an illegal string typed annotation key for the added timestamp. Worse, it causes the broker to mutate incoming symbol-keyed

[jira] [Commented] (QPID-5285) [AMQP 1.0] timestamped messages not supported

[ https://issues.apache.org/jira/browse/QPID-5285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17200681#comment-17200681 ] ASF GitHub Bot commented on QPID-5285: -- gemmellr commented on pull request #20: URL: