Installation steps

Gluesync NoSQL to NoSQL for Aerospike

Prerequisites

In order to have Gluesync working on your Aerospike instance you will need to have:

valid user credentials with permissions of writing to the target database

Basic configuration example

This module can be customized by using a configuration file, in JSON format. The file name to use must be specified as parameter when launching the app, with the -f or --file tokens. The file should be composed by union of common configuration file (see here Installation steps) and source/destination specific configuration:

{
  ...
  "aerospike": {
    "certificatesPath": "/path/to/certs/dir/cert.crt",
    "certificatesPassword": "change_me",
    "timeoutSeconds": 60,
    "indexReplicaCount": 0,
    "disableAuth": false
  },
}

Aerospike specific configurations are listed under the aerospike property:

certificatesPath (optional): the path to the certificate that need to be used when connecting to an Aerospike instance using a secure connection (TLS). If omitted, no certificate is used;
certificatesPassword (optional): if a certificate path is specified, then this value is passed as a keystore password;
timeoutSeconds (optional): number of seconds to set as timeout for operations involving communication with Aerospike. Default value is 60 seconds.;
disableAuth (optional), defaults to false: you can set that parameter to true in order to disable the authentication mechanism (as per the Aerospike docs) when you’re connecting to a development instance of Aerospike.

Aerospike bin names and entities names

Aerospike identifies the bin object with a key name that uniquely identifies an object stored in the database.

Since each bin key has a maximum lenght of 14 characters Gluesync will throw an exception in case you accidentaly have placed a longer entity name inside the sourceEntities list.