I am using Aerospike 3.4. community edition. It is known that aerospike supports only 1023 sets per namespace. In my situation, I may cross that limit. One way I could handle it may be include the set name with the PK and have everything in one set. In this case how do I iterate through the records in particular set. There may be other challenges in this approach. Can anyone help with this 1023 sets limitation?
Thanks in Advance.
In your case, you could use one set 'users' with the PK as client_id:email, and use a secondary index to optimize the requests to a specific client. This way you won't be restricted to sets limitation, and still have great performance on complex iterations.