Unable to correctly pass JSON object as inline message via CLI pulsar-client

[devinbost]

To Reproduce
Steps to reproduce the behavior:

1. Produce message via:
   bin/pulsar-client produce persistent://public/default/testInput -m '{ "test1" : "value1", "test2": "value2" }'
   Also try it like this:
   bin/pulsar-client produce persistent://public/default/testInput -m "{ 'test1' : 'value1', 'test2': 'value2' }"
   and like this:
   bin/pulsar-client produce persistent://public/default/testInput -m '"test1" : "value1", "test2": "value2"'

2. Try deserializing the message. In none of the above cases will the object deserialize correctly.

Save the following text into a file named test.json:
{ "test1" : "value1", "test2": "value2" }
4. Produce message via:
bin/pulsar-client produce persistent://public/default/testInput -f test.json
5. Message deserializes correctly.

Expected behavior
Passing JSON via inline message should produce the same result as passing JSON via file.

[devinbost]

It appears to be splitting the string on the comma into multiple messages.

[sijie]

@devinbost Are you interested in contributing a feature to produce JSON messages to pulsar-client CLI?

[devinbost]

@sijie Yes, I can work on this after I complete my current project.

[afedulov]

@devinbost Any progress on this issue? I see you already seem to have a corresponding fix on your fork?

[eolivelli]

There is an open PR of mine that implements this feature