> 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/release-1.6.0/build-with-pinot/data-modeling/logical-tables.md).

# Logical Tables

Use logical tables when one query name should span multiple physical Pinot tables without exposing the partitioning scheme to users.

Logical tables are a naming and routing layer on top of physical tables. They let you split data by region, age, or operating mode while keeping one user-facing table name.

Use a logical table when the split is an implementation detail, not part of the query contract. Keep the physical tables aligned on schema, and use a reference physical table only as a metadata anchor.

## When they help

Logical tables are most useful when you need one of these patterns:

Different physical tables per region or business unit.

Separate offline and realtime tables that still answer one business question.

Time-sliced tables that should be queried together.

## Design rules

Keep the underlying schemas aligned. Keep the logical name stable. Prefer this pattern only when the underlying split is operationally meaningful; do not use it to hide a modeling problem that should instead be solved with cleaner ingestion.

For hybrid-style layouts, make the time boundary explicit so Pinot does not double count overlapping data.

## Example pattern

```json
{
  "tableName": "orders",
  "brokerTenant": "DefaultTenant",
  "physicalTableConfigMap": {
    "ordersUS_OFFLINE": {},
    "ordersEU_OFFLINE": {}
  },
  "refOfflineTableName": "ordersUS_OFFLINE"
}
```

## Learn more

The original logical-table walkthrough lives in [Logical Table](/release-1.6.0/architecture-and-concepts/components/table/logical-table.md).

## What this page covered

This page covered when to use logical tables and how they hide physical table splits from readers.

## Next step

Read [Schema Evolution](/release-1.6.0/build-with-pinot/data-modeling/schema-evolution.md) if the schema needs to grow after the table is already in production.

## Related pages

* [Data Modeling](/release-1.6.0/build-with-pinot/data-modeling.md)
* [Schema and Table Shape](/release-1.6.0/build-with-pinot/data-modeling/schema.md)
* [Schema Evolution](/release-1.6.0/build-with-pinot/data-modeling/schema-evolution.md)
* [Original Logical Table Doc](/release-1.6.0/architecture-and-concepts/components/table/logical-table.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pinot.apache.org/release-1.6.0/build-with-pinot/data-modeling/logical-tables.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.