[
https://issues.apache.org/jira/browse/QPID-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579302#comment-13579302
]
Steven Hardy commented on QPID-4583:
------------------------------------
Aha - thanks, your comment "It is an AMQP 0-10 encoded map" made me look at the
spec again, which says "The value is encoded according to the rules defined by
the type code for that entry"
So I can see that any dict value which is a string must be < 65535, but if I
use a nested dict (instead of a json serialized dict), the limitation is
removed and the data structure I'm trying to send should be transferred
successfully without the binary encoding.
Thanks for your assistance figuring this out, since we both agree now the
implementation is aligned with the spec, this can be closed not-a-bug :)
> python-qpid limits map element size to 65535 bytes
> --------------------------------------------------
>
> Key: QPID-4583
> URL: https://issues.apache.org/jira/browse/QPID-4583
> Project: Qpid
> Issue Type: Bug
> Components: Python Client
> Affects Versions: 0.20
> Environment: Tested on Fedora 17, python-qpid-0.20-1.fc17.noarch
> Reporter: Steven Hardy
> Assignee: Gordon Sim
>
> It seems that we hit a limit of 65535 bytes when encoding a map via
> python-qpid, because the map elements are encoded as a str16 (write_map in
> codec010.py)
> Looking at the amqp 0-10 spec, it says "An encoded map may contain up to
> (4294967295 - 4) octets worth of encoded entries.", and I don't see any
> specified limit for individual map elements. This limitation does not appear
> to exist when testing on rabbitmq, so I'm wondering if it's possible to work
> out a way to remove this limit when using qpid.
> Reproducer:
> git clone https://gist.github.com/hardys/4951857
> cd 4951857
> python reproducer.py
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
