Is there a limit to how quickly a single Pulsar producer can produce messages?
Suppose I have read many messages from a source and intend to use a producer to send these messages. The producer typically sends the messages with millisecond differences between one message and the next, and sometimes it sends many messages in the same millisecond.
I am using bin/pulsar standalone command and getting “Could not find or load main class org.apache.pulsar.PulsarStandaloneStarter”
I am executing bin/pulsar standalone command. I am getting the below error:
Schema validation for producer using REST API does not validate schema [Apache Pulsar]
I’m having some issues with schema validation when using the REST API in Apache pulsar. When I use the python client, the data gets rejected if it does not adhere to the schema, (such as a required field missing). However, when I try the same using the same schema and the same topic using the REST API, the messages are accepted. To simplify, and reproduce the issue, I used the example provided here – https://pulsar.apache.org/docs/3.2.x/client-libraries-rest
How to achieve round robin user processing in Pulsar
we’re migrating from BullMQ to Pulsar and wondering how to achieve this behaviour in Pulsar
Pulsar command-line tool to consume and then exit at end of data
For Kafka, I can run this on the command line, with a timeout: