Python Pulsar client producer send should return messageId
See original GitHub issueIs your feature request related to a problem? Please describe.
The Python client does not return a Message ID for send
on producers. send_async
also seems to return a bogus message ID.
Describe the solution you’d like Match the behavior of the Java Pulsar client, which is documented to return a message ID.
Describe alternatives you’ve considered Outside of horrendous hacks involving creating a consumer at the same time and getting messages that way, I can’t think of any.
Additional context https://pulsar.apache.org/api/python/#pulsar.Producer.send https://pulsar.apache.org/api/client/org/apache/pulsar/client/api/Producer.html#send-T-
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Pulsar Python client
The following example creates a Python producer for the my-topic topic and sends 10 messages on that topic: import pulsar client = pulsar....
Read more >pulsar API documentation
The Pulsar Python client library is based on the existing C++ client library. All the same features are exposed through the Python interface....
Read more >Messaging - Apache Pulsar
Async send, The producer puts a message in a blocking queue and returns immediately. The client library sends the message to the broker...
Read more >Pulsar Clients
At this point the client sends a command to create producer/consumer to the broker, which will comply after having validated the authorization policy....
Read more >Pulsar Clients
Pulsar exposes a client API with language bindings for Java, Go, Python and ... At this point the client will send a command...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@yittg : #4811 is fixing the issue in C++ client and CGo client. For the python fix, it has to wait for #4811 to be merged.
This is fixed by #4811