Can I connect Parquet files or files in S3-style object storage to iDBQuery?
Yes — iDBQuery reads Parquet and other data files as file sources, including files held in S3-style object storage. You point iDBQuery at the file or bucket path with read-only access, and the data joins one live queryable model you ask in plain language, with cited answers.
Parquet (and other columnar/data files) connect to iDBQuery as file sources, whether they sit on disk or in S3-style object storage.
- You'd connect them by pointing iDBQuery at the file or a bucket/prefix path and providing read-only access to the storage.
- iDBQuery reads the Parquet schema directly — column names and types come for free — applies its semantic layer, and adds the data to your one live queryable model.
- Ask in plain language — *"What's total volume by region from the events files?"* — and iDBQuery writes and runs the query, returning a cited number, chart or table.
Parquet in object storage is a common pattern for exported events, logs, and data-lake extracts, so iDBQuery lets you query those files where they live without loading them into a warehouse first. You can point it at a prefix of many Parquet files and treat them as one table, and combine them in a single question with a live database, a warehouse, or a spreadsheet — one model, no ETL. Every figure is cited back to the exact rows and file it came from, so answers stay auditable. Grant read-only storage credentials, and deploy in your own VPC or air-gapped so the connection to your bucket never leaves your environment.
Updated 2026-06-22