The port-based-config section of aerospike-pulsar-outbound.yml

The port-based-config section allows alternate configurations based on which port received the change notification.

This is useful, for example, when you want to ship the same change notification to multiple destinations using a single connector cluster. To do this, configure XDR to ship to different ports on the same connector instance. Then set up each port to apply different configurations to dispatch the change notifications. For this you create one DC on XDR per connector port.

info

You can use any port between 1024 and 65335 for Aerospike, providing the port is not being used by an existing process.

For any service port you can configure any or all of the following differently from the global configuration

routing
format
bin-transforms
namespaces

Example

This example routes records to alternate destinations based on the incoming port.

port-based-config:
  8901:
    routing:
      mode: static
      destination: portOne

Example​

Example