> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/concepts/resources/depot/consume/querying.md).

# Querying

[Minerva](/concepts/resources/minerva.md) exposes Depot data through a Trino-compatible endpoint. Each configured Depot is available as a catalog for querying.

## How to consume a Depot for querying?

Below is a step-by-step guide on setting up and querying a Depot using Minerva.

### Prerequisites

Before querying a Depot through Minerva, the following should be ready:

* The Depot exists, and its source credentials are valid.
* Data Source connected via Depot should support Trino.
* A Minerva domain is available in the instance.
* A compute is available for the Minerva workload.
* The runtime user has access to the Depot.

### Example Minerva Resource

The following example exposes the S3, GCS, and ABFSS Depots through Minerva:

```yaml
name: minerva026
version: v1alpha
type: minerva
tags:
  - minerva
  - dataos:type:resource
  - dataos:type:tenant-resource
spec:
  compute: universe-compute
  depots:
    - address: "dataos://mys3lh26depot?purpose=rw"
    - address: "dataos://mygcslh26depot?purpose=rw"
    - address: "dataos://myabfsslh26depot?purpose=rw"
  runAsUser: harshnagartmdcio
  coordinatorEnvs:
    VERBOSE_CONFIG: "true"
  workerEnvs:
    VERBOSE_CONFIG: "true"
```

### Query the data

Once Minerva is ready, you can query using the Workbench interface.

For full Minerva configuration details, see [Minerva](/concepts/resources/minerva.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://v2.dataos.info/concepts/resources/depot/consume/querying.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.