# Offline store

An offline store is an interface for working with historical time-series feature values that are stored in [data sources](https://docs.feast.dev/v0.43-branch/getting-started/concepts/data-ingestion). The `OfflineStore` interface has several different implementations, such as the `BigQueryOfflineStore`, each of which is backed by a different storage and compute engine. For more details on which offline stores are supported, please see [Offline Stores](https://docs.feast.dev/v0.43-branch/reference/offline-stores).

Offline stores are primarily used for two reasons:

1. Building training datasets from time-series features.
2. Materializing (loading) features into an online store to serve those features at low-latency in a production setting.

Offline stores are configured through the [feature\_store.yaml](https://docs.feast.dev/v0.43-branch/reference/offline-stores). When building training datasets or materializing features into an online store, Feast will use the configured offline store with your configured data sources to execute the necessary data operations.

Only a single offline store can be used at a time. Moreover, offline stores are not compatible with all data sources; for example, the `BigQuery` offline store cannot be used to query a file-based data source.

Please see [Push Source](https://docs.feast.dev/v0.43-branch/reference/data-sources/push) for more details on how to push features directly to the offline store in your feature store.


---

# 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.feast.dev/v0.43-branch/getting-started/components/offline-store.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.