FAQ - Feature Key location for connectors

The Aerospike Knowledge Base has moved to https://support.aerospike.com. Content on https://discuss.aerospike.com is being migrated to either https://support.aerospike.com or https://docs.aerospike.com. Maintenance on articles stored in this repository ceased on December 31st 2022 and this article may be stale. If you have any questions, please do not hesitate to raise a case via https://support.aerospike.com.

FAQ - Feature Key location for connectors

Detail

For Aerospike server features the feature key is located by default in /etc/aerospike. Some Aerospike Connectors require a feature key. Where are these keys located?

Answer

Kafka - Outbound

This is keyed via the presence of asdb-change-notification in the server feature file (feature-key-file configuration parameter).

Kafka - Inbound

The feature key location is specified in the properties file using the feature-key-file property.

JMS - Outbound

This is keyed via the presence of asdb-change-notification in the server feature file (feature-key-file configuration parameter).

JMS - Inbound

The feature key location is specified in the properties file using the feature-key-file property.

Spark

Spark requires the feature key for the Connector but not for the Aerospike database. In effect the Connector works as both an ‘inbound’ and ‘outbound’ Connector as it can exchange data between Spark and Aerospike in a bi-directional manner. The path to the Connector side feature key is set by aerospike.featureKey in the properties file. If there is no path specified, the Connector will try and read the file from HDFS.

Notes

  • The location of the server feature key can be changed by using the server configuration parameter feature-key-file
  • The server feature key is read at startup. Addition of new features will require a node restart.

Keywords

CONNECTOR LICENSE SERVER FEATURE-KEY-FILE

Timestamp

June 2020