Using CHouse UIExplorer
Exports
Download result sets and table samples as CSV, JSON or TSV from the workspace and explorer.
Result sets leave CHouse UI as files — CSV, JSON or TSV — from the query workspace and the explorer.
Where export lives
| Surface | What you export |
|---|---|
| SQL editor result grid | The current result set (subject to the row cap) |
| Data preview | The sampled rows of a table |
| Query logs / monitoring grids | Selected rows in some views |
The Download dialog lets you choose format and scope before the file is produced.
Formats
| Format | Best for | Notes |
|---|---|---|
| CSV | Spreadsheets, BI tools | Quoting/escaping per RFC 4180 |
| JSON | APIs, further processing | Full-fidelity types where possible |
| TSV | ClickHouse-native pipelines | Tab-separated, minimal quoting |
How it works
- Export requests run through the same security pipeline as queries —
table:select/query:executeplus data access rules apply - The server streams the file; the browser never talks to ClickHouse directly
- Row caps apply: exporting "everything" of a huge table will export what the query/preview returned, not the full table — write an explicit query for full extracts
- Analyst role and below typically have select+export; guests may be read-only depending on your permission setup
Auditability
Exports are logged in the audit log like any other action — who exported what and when.
Tip: For recurring extracts, save the query as a saved query or automate it with Scheduled queries / the CLI instead of hand-pulling files.