# Data modeling

Pinot works best when the table shape is clear before data lands. Start here to understand the structure that every ingestion and query decision depends on: schema design, table composition, logical-table layout, and how schemas evolve without breaking existing pipelines.

If you need dense JSON config or controller endpoints, jump to the [Reference](/reference/reference.md) section instead. This section stays narrative and decision-oriented.

## Start Here

* [Schema and Table Shape](/build-with-pinot/data-modeling/schema.md)
* [Logical Tables](/build-with-pinot/data-modeling/logical-tables.md)
* [Schema Evolution](/build-with-pinot/data-modeling/schema-evolution.md)

## Related Existing Docs

* [Schema](/architecture-and-concepts/components/table/schema.md)
* [Table](/architecture-and-concepts/components/table.md)
* [Logical Table](/architecture-and-concepts/components/table/logical-table.md)
* [Schema Evolution Tutorial](/tutorials/data-ingestion/schema-evolution.md)
* [Schema Reference](/reference/configuration-reference/schema.md)
* [Table Reference](/reference/configuration-reference/table.md)

## What this page covered

This landing page defines the scope of Pinot data modeling and points to the core pages that matter first.

## Next step

Read [Schema and Table Shape](/build-with-pinot/data-modeling/schema.md) to lock in the table structure before designing ingestion.

## Related pages

* [Schema and Table Shape](/build-with-pinot/data-modeling/schema.md)
* [Logical Tables](/build-with-pinot/data-modeling/logical-tables.md)
* [Schema Evolution](/build-with-pinot/data-modeling/schema-evolution.md)


---

# Agent Instructions: 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:

```
GET https://docs.pinot.apache.org/build-with-pinot/data-modeling.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.