Hi
As the limitations page conveys, currently this is limited to 2^32 objects.
During a support case over the holidays a support engineer alluded to the fact that this is on your radar, but no information as to when we may see this in the wild was available.
Actual number limited by RAM and storage. Every record takes 64 bytes for the index entry. The index entry is ONLY stored in RAM. The key itself is not actually stored in the index, but the hash of the key (using RIPE-MD 160 algorithm) is. This hash with overhead takes exactly 64 bytes. The maximum number of records per namespace on a given node is limited to 4,294,967,296 on the Community Edition (2^32 due to 4 bytes used for storing references), and 549,755,813,888 on the Enterprise Edition (2^39) * . This represents 32TiB of RAM.
The value of the 2^39 number of records can be reached using Aerospike Server Enterprise Edition version 4.2.0.2 or newer, and having index-stage-size set to 16G.