RealtimeTrigger

Consume a message in real-time from Pulsar topics and create one execution per message.

If you would like to consume multiple messages processed within a given time frame and process them in batch, you can use the io.kestra.plugin.pulsar.Trigger instead.

yaml
type: "io.kestra.plugin.pulsar.RealtimeTrigger"

Consume a message from a Pulsar topic in real-time.

yaml
id: pulsar
namespace: company.team

tasks:
  - id: log
    type: io.kestra.plugin.core.log.Log
    message: "{{ trigger.value }}"

triggers:
  - id: realtime_trigger
    type: io.kestra.plugin.pulsar.RealtimeTrigger
    topic: kestra_trigger
    uri: pulsar://localhost:26650
    deserializer: JSON
    subscriptionName: kestra_trigger_sub

Dynamic YES

Default STRING

Possible Values

STRINGJSONBYTES

Deserializer used for the value.

Dynamic YES

The subscription name.

Using subscription name, we will fetch only records that haven't been consumed yet.

Dynamic YES

Default Exclusive

Possible Values

ExclusiveSharedFailoverKey_Shared

The subscription type.

Dynamic YES

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

Dynamic YES

Authentication token.

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

SubType

Dynamic NO

List of conditions in order to limit the flow trigger.

Dynamic YES

The consumer name.

SubType string

Dynamic YES

Add all the properties in the provided map to the consumer.

Dynamic YES

Add a public encryption key to the producer/consumer.

Dynamic YES

Default Earliest

Possible Values

LatestEarliest

The position of a subscription to the topic.

Dynamic YES

JSON string of the topic's schema

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

Dynamic YES

Default NONE

Possible Values

NONEAVROJSON

The schema type of the topic

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

SubType string

Dynamic NO

Possible Values

CREATEDRUNNINGPAUSEDRESTARTEDKILLINGSUCCESSWARNINGFAILEDKILLEDCANCELLEDQUEUEDRETRYINGRETRIEDSKIPPED

List of execution states after which a trigger should be stopped (a.k.a. disabled).

Dynamic NO

TLS authentication options.

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

Dynamic YES

Pulsar topic(s) where to consume messages from.

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

Format date-time

SubType string

Dynamic YES

The ca certificate.

Must be a base64-encoded pem file.

Dynamic YES

The client certificate.

Must be a base64-encoded pem file.

Dynamic YES

The key certificate.

Must be a base64-encoded pem file.

​Realtime​Trigger

RealtimeTrigger