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 - Where are operations on HyperLogLog datatypes processed?
Detail
Hyperloglog datatypes can be used to form estimations of set membership across large datasets allowing simalarity, membership and cardinality of intersections or unions of sets to be returned to a client application. Where is the processing of operations on the HLL bin type done, server or client?
Answer
The processing of operations across HLL bin types is done completely server side. Only results are returned to the client. The operation (for example the union or intersection computation) happens with an HLL bin on a single record and will take place on the server node holding the partition for that record. The second participant (argument) in the operation is provided by the client api as a list of HLLs. To make that list of HLLs, the application may fetch those from another (one or more) record’s HLL bins.
Notes
- For further details on the HLL related APIs, refer to the HyperLogLog documentation page.
Keywords
HYPERLOGLOG PROCESS SERVER CLIENT
Timestamp
December 2020