dionjansen opened a new issue #129: URL: https://github.com/apache/pulsar-client-node/issues/129
When producing messages with message properties from the node client producer and consuming them with the [pulsar-dotpulsar](https://github.com/apache/pulsar-dotpulsar) consumer it seems that the properties are mixed lost inside the message body. #### Reproduce: 1. Modify the [producer.js](https://github.com/apache/pulsar-client-node/blob/master/examples/producer.js) to include message properties, say: `{foo: "bar"}` 1. Modify the [Consuming](https://github.com/apache/pulsar-dotpulsar/blob/master/samples/Consuming/Program.cs) sample in dotpulsar to read and log the properties, e.g.: ` Console.WriteLine("Received: " + data + ", Props Count: " + message.Properties.Count);` 1. Run both You'd expect the consumer to log to read: ```bash Received my-message-0, Props Count: 1 Received my-message-1, Props Count: 1 # ... etc ``` But what we actually see: ```bash Received foobar my-message-0, Props Count: 0 Received foobar my-message-1, Props Count: 0 # ... etc ``` According to the maintainer of [pulsar-dotpulsar](https://github.com/apache/pulsar-dotpulsar) there seems to be a difference in how the raw payload is created by the node-lib, in that the metadata properties of the message are being send as part of the payload. It is unclear if this is a bug or perhaps a missing feature that [pulsar-dotpulsar](https://github.com/apache/pulsar-dotpulsar) is not making use of (yet). #### Additional info I did the following checks between different clients to check if this issue can be seen in different combinations: - node-client > dotnet-client: does not work 👎 - node-client > python-client: works 👍 - node-client > java-client: works 👍 - python-client > dotnet-client: works 👍 Also this issue is only reproducible if the messages are not batched, sending a batch of messages in the above scenario works as expected. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
