Skip to main content
Loading

Namespace configuration for Pulsar Outbound

Namespace configuration.

The namespaces can be configured with bin transforms, routing and format. The configuration is a map of the namespace name to its configuration.

OptionRequiredDescription
bin-transformsnoBin transforms for the namespace.
routingnoRouting for the namespace.
formatnoFormat for the namespace.
setsnoMap of set name to bin-transform, routing and format configuration.

For a given record the order of preference for picking the configuration for the bin-transforms, routing and format are:

  1. set, if configured
  2. namespace, if configured
  3. default

WARNING

  • If the route or format are not specified for a record then the record is skipped.
  • Currently, set name is not shipped for a delete, so a set specific routing can never be applied to a delete. In this case the writes will be routed as per set configuration but the deletes will be routed as per the namespace configuration, in which case the writes and deletes can be routed to different routes.

Example

routing:
mode: static
destination: all-data

namespaces:
users:
format:
mode: json
sets:
premium:
routing:
mode: static
destination: users-sets
bin-transforms:
transforms:
- uppercase

As per the above configuration

NamespaceSetRoutingFormatBin TransformsAction
usersall-datajsonWrite record to all-data topic in JSON format.
userspremiumusers-setsjsonuppercaseConvert all bin names to upper case and write record to users-sets topic in JSON format
placesSkip record, since routing or format information is missing.