Consume
Consume messages from Pulsar topic(s).
type: "io.kestra.plugin.pulsar.Consume"id: pulsar_consume
namespace: company.team
tasks:
- id: consume
type: io.kestra.plugin.pulsar.Consume
uri: pulsar://localhost:26650
topic: test_kestra
deserializer: JSON
subscriptionName: kestra_flow
STRINGSTRINGJSONBYTESDeserializer used for the value.
PT2SdurationDuration waiting for record to be polled.
If no records are available, the maximum wait to wait for a new record.
ExclusiveExclusiveSharedFailoverKey_SharedThe subscription type.
Pulsar topic(s) where to consume messages from.
Can be a string or a list of strings to consume from multiple topics.
Authentication token.
Authentication token that can be required by some providers such as Clever Cloud.
The consumer name.
Add all the properties in the provided map to the consumer.
Add a public encryption key to the producer/consumer.
EarliestLatestEarliestThe position of a subscription to the topic.
durationThe 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.
JSON string of the topic's schema
Required for connecting with topics with a defined schema and strict schema checking
NONENONEAVROJSONThe schema type of the topic
Can be one of NONE, AVRO or JSON. None means there will be no schema enforced.
The subscription name.
Using subscription name, we will fetch only records that haven't been consumed yet.
TLS authentication options.
You need to use "pulsar+ssl://" in serviceUrl to enable TLS support.
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
Number of messages consumed.
uriURI of a Kestra internal storage file containing the consumed messages.
The ca certificate.
Must be a base64-encoded pem file.
The client certificate.
Must be a base64-encoded pem file.
The key certificate.
Must be a base64-encoded pem file.