Query Engine is a Kubernetes-native SQL engine for high-concurrency analytics.
It runs inside your cloud account and reads Iceberg, Delta Lake, Hudi and Hive tables where they already live. You do not need Ingest Engine to use it.ServerlessCloudPremSelf-managedSome pages differ by deployment. Look for the tag next to a page in the sidebar.
Run your first query
SQL command reference
Built for
High concurrency
Many users running many queries at the same time, with clusters that scale with load.
Complex SQL
Joins, window functions and aggregations over large fact tables.
Cost discipline
Pay for what you use. Clusters suspend when they’re idle.
How teams use it
- BI dashboards at the scale of thousands of concurrent users, with sub-second query times.
- Operational analytics for product, ops and revenue teams that need fresh answers, not warehouse refresh cycles.
- Ad-hoc exploration on data lakes too large to load into a traditional warehouse.
- AI and ML feature pipelines that run close to the data.
How it works
Query Engine reads your tables where they already live and answers SQL from the tools you use. For the details, see How Query Engine works and the architecture.01 · Connect
Connect a catalog
AWS Glue, Hive Metastore, Unity Catalog, Apache Polaris, Iceberg REST, S3 Tables, Microsoft Fabric
02 · Run
Create a cluster
Cluster size, load-based scaling, auto suspension, query timeout
03 · Query
Query from your tools
Query Editor, notebooks, Python, JDBC, PostgreSQL protocol, Tableau, Power BI, Metabase
What do you want to do?
Get started
Run your first query
The full path, from sign-up to your toolsChoose Serverless or CloudPremRun your first queryConnect data
Point it at your tables
Register and manage catalogsCross-account catalog accessTable formats: Iceberg, Delta Lake, Hive, HudiRun clusters
Size and operate
Create and manage a clusterSizing, scaling and auto suspensionCloudPrem cluster operationsQuery
Run SQL from your tools
Query Editor and resultsQuery e6data from PythonJDBC, Tableau, Power BI, MetabaseSecure and govern
Control who sees what
Catalog-level access controlMask columns and filter rowsAudit logTroubleshoot and reference
Look it up
Error codes and known limitationsSQL functions and data typesREST API, generated from the OpenAPI specOptional add-ons
Optional · /ingest/Add live data with Ingest Engine/agentflow/Run agent workflows on your tables with AgentFlowShared · /platform/Set up cloud accounts, access control and SSO in Platform
Docs owner: Query teamReport a problem with this page