Browsing data

Note

In Aerospike, a namespace is similar to a database, a set is similar to a table, and a record is similar to a row. Unlike relational databases, Aerospike is schemaless: records in the same set can have different bins (columns).

For a deeper explanation, see the Aerospike data model documentation.

Navigation hierarchy

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.

Record cards

Each record card shows:

• Key and digest: The record’s user key (if stored) and its digest (truncated hex hash), displayed in the card header. 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:
  • Gen: The generation count (number of times the record has been written).
  • Exp: The record’s expiration. Shows Never for records with no TTL, or the expiration timestamp.
  • Node: The cluster node ID that owns this record.
  • Part: The partition ID where this record is stored.
• Show N more bins: If a record has more bins than the default display limit, click this link to reveal the rest.

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 at any depth. 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.

Pagination

Records are paginated to keep the interface responsive. The default page size is 25 records per page. You can change this in Settings (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 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).
• Digest: The 20-byte hash that Aerospike uses internally to identify every record. Enter the digest as a hex string.

Next steps

• Filtering records
• Editing records
• Loading sample data