Skip to content
Queria Docs
English
Esc
↑↓navigate↵open⌘Jpreview
On this page

Hand data to BI tools and notebooks

Export filtered results to Parquet / CSV and open them directly in Tableau, Excel, or pandas

The quickest way to use Queria data in your existing tools is not a live connection setup — it’s handing over a file. Filter down to what you need with the Queria CLI, export to Parquet / CSV, and the recipient just opens the file in their usual tool. No connectors, no drivers.

Filter first, then export

Rather than handing over a whole table, narrow it to the columns and rows you need with SQL, then write to --out:

queria sql "
  SELECT area_name, year, value AS population
  FROM e_stat.ssds.a_pref_population
  WHERE item_name = 'A1101_総人口' AND year >= 2015
" --out population.parquet

Use a .csv extension to export CSV instead. The smaller the file, the snappier the receiving tool.

Open in Tableau

Tableau Desktop opens text files (CSV) as-is, and 2024.2 or later opens Parquet files directly.

Once you start building out a workbook, switch from manual file refreshes to a live connection to track catalog updates.

Open in Excel or spreadsheets

Export CSV and it opens straight into Excel or Google Sheets:

queria sql "SELECT ..." --out monthly.csv

Read with pandas / Polars

The receiving notebook doesn’t need the queria package installed — it just reads the Parquet:

import pandas as pd

df = pd.read_parquet("population.parquet")

To query directly from the notebook instead, the Python API takes you straight to a DataFrame with conn.sql(...).df().

Keep it reproducible

Sharing only the file tends to lose “how was this made?”. Keep the generating command as a script next to the file so anyone can rebuild it:

#!/usr/bin/env bash
# make-population.sh — how population.parquet is produced
queria sql "
  SELECT area_name, year, value AS population
  FROM e_stat.ssds.a_pref_population
  WHERE item_name = 'A1101_総人口' AND year >= 2015
" --out population.parquet

When you want it refreshed on a schedule, put this script on cron — see Embed in shell pipelines.

Was this page helpful?