You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If compression is enabled for a producer but batching is off, messages will be compressed, but will not be uncompressed again. This appears to be related to the chunking code in producer_partion.go introduced with #805 which compresses by default, but does not appear to set MessageMetadata.Compression nor test for it, so the consumer is not aware that messages are compressed, and will assume they are not.
The simplest case to reproduce this is to simply turn batching off and enable compression, however enabling compression in TestLargeMessage also causes it to fail, meaning chunking will be broken if compression is enabled.
If compression is enabled for a producer but batching is off, messages will be compressed, but will not be uncompressed again. This appears to be related to the chunking code in
producer_partion.go
introduced with #805 which compresses by default, but does not appear to setMessageMetadata.Compression
nor test for it, so the consumer is not aware that messages are compressed, and will assume they are not.The simplest case to reproduce this is to simply turn batching off and enable compression, however enabling compression in
TestLargeMessage
also causes it to fail, meaning chunking will be broken if compression is enabled.Result:
Expected behavior
Success
Actual behavior
Failure. Message has not been uncompressed.
Steps to reproduce
test-case is above.
System configuration
Pulsar version: 2.8.
The text was updated successfully, but these errors were encountered: