Documentation
Object Storage

Query object storage

Altertable can query data that already lives in Amazon S3, Cloudflare R2, Google Cloud Storage, or another S3-compatible bucket. Map the files once, then use the same SQL engine and query interfaces you use for Altertable catalogs.

Object storage queries run in place. Altertable reads mapped files from the connected bucket.

What you can query

Source
Best fit
Learn more
Parquet, CSV, or JSON files
Query file paths and prefixes as external tables
Apache Iceberg datasets
Query datasets through Iceberg table metadata
Amazon S3 table buckets
Query AWS-managed Iceberg table buckets

Query mapped tables

After you map object storage, query the exposed tables with fully qualified names:

SELECT
event_name,
count(*) AS event_count
FROM bucket_exports.main.events
WHERE event_date >= DATE '2026-01-01'
GROUP BY event_name
ORDER BY event_count DESC;

Mapped object-storage tables can be joined with Altertable-managed catalogs and other external catalogs:

SELECT
customers.segment,
count(*) AS events
FROM bucket_exports.main.events
JOIN analytics.main.customers
ON events.customer_id = customers.customer_id
GROUP BY customers.segment;

Query from any Altertable interface

Use object-storage tables from:

Query performance

For large object-storage datasets, prefer columnar formats such as Parquet or Iceberg, keep partitions predictable, and filter on partition columns when possible. Altertable can query CSV and JSON files, but columnar formats usually scan less data and return results faster.

Crafted with <3 by former Algolia × Front × Sorare builders© 2026 AltertableTermsPrivacySecurityCookies