# Limitations

## Feast API

| Limitation                                                                                                                                                                                                                                           | Motivation                                                                             |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| Features names and entity names cannot overlap in feature table definitions                                                                                                                                                                          | Features and entities become columns in historical stores which may cause conflicts    |
| <p>The following field names are reserved in feature tables</p><ul><li><code>event\_timestamp</code></li><li><code>datetime</code></li><li><code>created\_timestamp</code></li><li><code>ingestion\_id</code></li><li><code>job\_id</code></li></ul> | These keywords are used for column names when persisting metadata in historical stores |

## Ingestion

| Limitation                                                                                                                                                                                                                                                                                      | Motivation                                                 |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- |
| Once data has been ingested into Feast, there is currently no way to delete the data without manually going to the database and deleting it. However, during retrieval only the latest rows will be returned for a specific key (`event_timestamp`, `entity`) based on its `created_timestamp`. | This functionality simply doesn't exist yet as a Feast API |

## Storage

| Limitation                                          | Motivation                                                                                                                                                                                    |
| --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Feast does not support offline storage in Feast 0.8 | As part of our re-architecture of Feast, we moved from GCP to cloud-agnostic deployments. Developing offline storage support that is available in all cloud environments is a pending action. |


---

# 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.11-branch/feast-on-kubernetes/reference-1/limitations.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.