The namespaces section of the Aerospike ESP Outbound YAML file

You can use the namespaces section of the /etc/aerospike-esp-outbound/aerospike-esp-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.
record-ordering	no	Record ordering 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:

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

caution

• If the route is not specified for a record, then the record is skipped.
• Currently, set name does not ship for a delete, so set-specific routing is never applied to a delete. In this case, the writes are routed according to set configuration, but the deletes are routed according to the namespace configuration. The writes and deletes are sent 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

Details of the preceding example:

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.