Browsing data

For the complete documentation index see: llms.txt

All documentation pages available in markdown.

Aerospike Voyager organizes data in the same hierarchy as Aerospike itself. You drill down through four levels:

Clusters overview

The top-level view lists all connected clusters with their connection status (connected, disconnected, error). Click a cluster to see its namespaces.

Namespace overview

Lists all namespaces in the selected cluster. Each namespace card shows the number of sets and storage usage.

Set view

Lists all sets within a namespace along with their record counts. Click a set to browse its records.

Records view

Records render as expandable cards in a scrollable list. Each card shows the record’s bins and metadata. Refresh and Last updated time are next to the results count, the same as on the cluster, namespace, and set views. The filter row sits between the page controls and the records. See Filtering records.

Record cards

Each record card shows:

User key and digest: The record’s user key (if stored) and its digest (truncated hex hash), displayed in the card header. When the record stores a user key, a badge beside it names the user key’s Aerospike type: string, integer, or blob. No badge appears when the record holds no user key. Click the copy icon next to the digest to copy the full value.
Bins: The key-value pairs stored in the record. Each bin displays its name, value, and a type badge.
Metadata chips: Summary information in the card header. Hover over a chip for a description.
- Gen: The generation count, which increases each time the record is updated.
- Exp: Time until the record expires, such as 11h 40m, or Never for a record with no expiration.
- Size: The stored size of the record, such as 320 B or 12.4 KB.
- Updated: How long ago the record was last updated, such as 3d ago.
Show N more bins: If a record has more bins than the default display limit, click this link to reveal the rest.

Size and Updated appear only when the cluster reports them. On a cluster where every node runs Aerospike Database 7.0 and later, Size is the record size. On earlier or mixed-version clusters, it is the larger of the record’s device and memory size.

When a filter uses a record metadata field, such as $.ttl() or $.recordSize(), the matching chip is highlighted on every card in the result. See Filter on record metadata.

Click the See all metadata icon in the card header to open the Record metadata popover. It groups the record’s metadata under two headings:

Record: Generation, Expires (the expiry time and how long until it arrives, or Never), Last updated (the time of the last update and how long ago it was), and Size.
Location: Node, the cluster node that owns the record, and Partition, the partition that stores it.

Record metadata popover open beside a sample_users record card, showing Generation 1, Expires Never, Last updated Sep 4 with 23d ago, and Size 320 B under Record, and Node and Partition 2048 under Location

Copy a record as JSON

Click the Copy as JSON icon in the card header to copy the whole record to the clipboard as JSON. The JSON includes the user key and its type, the digest, the bins, and the record’s metadata. A confirmation names the record that was copied.

Records that cannot be displayed

If a bin value is too large or too unusual for the record view, such as a very wide list or map, the card reads This record could not be displayed. The record is unchanged, and the rest of the data browser keeps working. Click Copy record JSON to copy the record and inspect it elsewhere.

Type badges

Voyager displays the following Aerospike data types: String, Integer, Double, Boolean, List, Map, Bytes, GeoJSON, and HLL. Each bin value carries a type badge in the UI (rendered with the lowercase identifier, for example string, integer, double).

Nested data expansion

List and Map bins can contain nested structures, and Voyager’s tree view can display them regardless of how deeply they are nested. Click the expand arrow next to a List or Map bin to drill into its contents using an inline tree view. Each nested level indents further and displays its own type badges. Use the Expand bins one level and Collapse bins one level buttons in each record card’s header to expand or collapse all bins at once.

sample_users record card with the address map expanded to show city, state, street, and zip as string values, and the Gen, Exp, Size, and Updated chips in the card header

Pagination

Records are paginated to keep the interface responsive. The default page size is 25 records per page. You can change this in Preferences > General > Default records per page (range: 1 to 50 records per page). Use the pagination controls in the toolbar above the records to navigate between pages.

Record lookup

To jump directly to a specific record, click the Search by user key or digest icon in the toolbar above the records. You can search by:

User key: The application-level key you used when writing the record (available only if the record was written with the “send key” option enabled). Searching for a number can return two records, one stored under the string and one under the integer. See String and integer user keys.
Digest: The 20-byte hash that Aerospike uses internally to identify every record. Enter the digest as a hex string.

String and integer user keys

A user key’s type is part of the record’s identity in Aerospike. A record stored under the string 42 and a record stored under the integer 42 are two different records, and both can exist at the same time.

You do not pick a type when you search. Voyager looks your term up both ways and returns whichever records exist, so a search for 42 can return two results. The badge on each record card names the user key type that record holds.

Only plain digits are searched as an integer user key, up to the size of a 64-bit signed integer. A term such as 0x2A, 42.0, or 4.2e1 is searched as a string user key only.

Voyager can show a record whose user key is a byte array, badged blob, but cannot create one.

If a lookup finds no record, see Record lookup finds nothing.

Troubleshoot

Symptom	Cause	Fix
A record card has no Size or Updated chip	The cluster did not report the value. Size needs Aerospike Database 7.0 and later on every node.	No fix. Voyager shows the chip when the cluster reports the value.
This record could not be displayed	A bin value is too large or too unusual for the record view	Click Copy record JSON and inspect the record elsewhere. The record is unchanged.
The Search by user key or digest icon is unavailable	A filter is applied	Click Clear all in the filter row.
The filter row is unavailable	A user key or digest lookup is active	Clear the lookup.
A lookup finds no record	The key type or digest does not match a stored record	See Record lookup finds nothing.

For other problems, see Voyager troubleshooting.