Configure namespaces for the JMS outbound connector

You can use the namespaces section of the /etc/aerospike-jms-outbound/aerospike-jms-outbound.yml to override settings for bin-name transformations, routing modes, and serialization formats.

Option	Required	Description
`bin-transforms`	no	Bin transforms for the namespace.
`routing`	no	Routing for the namespace.
`format`	no	Format for the namespace.
`sets`	no	Map 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:

set, if configured
namespace, if configured
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

Namespace	Set	Routing	Format	Bin Transforms	Action
`users`		`all-data`	`json`		Write record to all-data topic in JSON format.
`users`	`premium`	`users-sets`	`json`	`uppercase`	Convert all bin names to upper case and write record to users-sets topic in JSON format
`places`					Skip record, since routing or format information is missing.