Apache Pulsar
Configuration Options
Required Options
endpoint(required)
Endpoint to which the pulsar client should connect to.
| Type | Syntax | Default | Example |
|---|---|---|---|
| string | literal | ["pulsar://127.0.0.1:6650"] |
inputs(required)
A list of upstream source or transform
IDs. Wildcards (*) are supported.
See configuration for more info.
| Type | Syntax | Default | Example |
|---|---|---|---|
| array | literal | ["my-source-or-transform-id","prefix-*"] |
encoding(required)
Configures the encoding specific sink behavior.
| Type | Syntax | Default | Example |
|---|---|---|---|
| hash | literal | [] |
topic(required)
The Pulsar topic name to write events to.
| Type | Syntax | Default | Example |
|---|---|---|---|
| string | literal | ["topic-1234"] |
type(required)
The component type. This is a required field for all components and tells Vector which component to use.
| Type | Syntax | Default | Example |
|---|---|---|---|
| string | literal | ["pulsar"] |
Advanced Options
auth(optional)
Options for the authentication strategy.
| Type | Syntax | Default | Example |
|---|---|---|---|
| hash | literal | [] |
healthcheck(optional)
Health check options for the sink.
| Type | Syntax | Default | Example |
|---|---|---|---|
| hash | [] |
How it Works
State
This component is stateless, meaning its behavior is consistent across each input.
Health checks
Health checks ensure that the downstream service is accessible and ready to accept data. This check is performed upon sink initialization. If the health check fails an error will be logged and Vector will proceed to start.