> For the complete documentation index, see [llms.txt](https://docs.pinot.apache.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pinot.apache.org/build-with-pinot/connectors-clients-apis/query-engines.md).

# Query engines

Use federated query engines when Pinot is one source in a broader SQL stack and you want to join or compare it with other systems. These integrations are the right fit when a data platform already standardizes on Trino for interactive analytics.

## What belongs here

| Engine | Best for                                               | Notes                                                                                                  |
| ------ | ------------------------------------------------------ | ------------------------------------------------------------------------------------------------------ |
| Trino  | Interactive federated SQL across multiple data sources | The current guide covers Kubernetes deployment, Pinot catalog configuration, and CLI-based validation. |

{% hint style="info" %}
**Presto support removed**: The Pinot Presto connector, Docker images, and Helm chart have been removed as of [apache/pinot#17947](https://github.com/apache/pinot/pull/17947). Trino (the Presto successor) is the recommended query engine for federated SQL over Pinot.
{% endhint %}

## Detailed docs

* [Trino](/build-with-pinot/connectors-clients-apis/query-engines/trino.md)
* [Query engines on Kubernetes](/build-with-pinot/connectors-clients-apis/query-engines/query-engines-kubernetes.md)

## What this page covered

This page covered the federated SQL engine most commonly used to query Pinot alongside other systems.

## Next step

Use the linked Trino guide, then verify the catalog configuration with a small query before rolling it into production.

## Related pages

* [BI tools](/build-with-pinot/connectors-clients-apis/bi-tools.md)
* [REST / gRPC APIs](/build-with-pinot/connectors-clients-apis/rest-grpc-apis.md)
* [Querying Pinot](/build-with-pinot/querying-and-sql/querying-pinot.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pinot.apache.org/build-with-pinot/connectors-clients-apis/query-engines.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.