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

The port-based-config section allows alternate configurations based on which port received the change notification. This is useful if you wish to ship the same change notification to multiple destinations using a single connector cluster, for example. You could configure XDR to ship to different ports on the same connector instance and have each port apply different configuration to dispatch the change notifications. For this you create one DC on XDR per connector port.

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

attributes
bin-transforms
routing
format
ordering key
namespaces

Example

For example, based on the incoming port you could route records to alternate topics as follows:

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

Example​

Example