Deserializer used for the value.

Pulsar topic(s) where to consume messages from.

Can be a string or a list of strings to consume from multiple topics.

Connection URLs.

You need to specify a Pulsar protocol URL.

• Example of localhost: pulsar://localhost: 6650
• If you have multiple brokers: pulsar://localhost: 6650,localhost: 6651,localhost: 6652
• If you use TLS authentication: pulsar+ssl://pulsar.us-west.example.com: 6651

Authentication token.

Authentication token that can be required by some providers such as Clever Cloud.

The maximum duration waiting for new record.

It's not a hard limit and is evaluated every second.

The maximum number of records to fetch before stopping.

It's not a hard limit and is evaluated every second.

Position the reader on a particular message.

The first message read will be the one immediately after the specified message. If no since or messageId are provided, we start at the beginning of the topic.

Duration waiting for record to be polled.

If no records are available, the maximum wait to wait for a new record.

JSON string of the topic's schema

Required for connecting with topics with a defined schema and strict schema checking

The schema type of the topic

Can be one of NONE, AVRO or JSON. None means there will be no schema enforced.

The initial reader positioning can be set at specific timestamp by providing total rollback duration.

So, broker can find a latest message that was published before given duration. eg: since set to 5 minutes (PT5M) indicates that broker should find message published 5 minutes in the past, and set the initial position to that messageId.

TLS authentication options.

You need to use "pulsar+ssl://" in serviceUrl to enable TLS support.