--- title: "Manage a table in Lakehouse Manager" description: "There are six table interactions in total. ' icon after clicking on the table" url: https://docs.ovhcloud.com/pl/guides/public-cloud/data-platform/lakehouse-manager-manage-tables lang: pl lastUpdated: 2026-09-14 --- > For AI agents: the complete documentation index is available at https://docs.ovhcloud.com/pl/llms.txt, the full documentation bundle is available at https://docs.ovhcloud.com/pl/llms-full.txt. # Manage a table in Lakehouse Manager ## Objective There are six table interactions in total. When in Canvas-view, display the first three options by clicking on a table and, display the other three, by clicking on the '**...**' icon after clicking on the table. In List-view, just scroll over the table to display all available interactions. ![MTA1](/images/public-cloud/data-platform/product/lakehouse-manager/tables/picts/tables-interactions.png) - ➕ [Add a new attribute](#add-a-new-attribute) - [Attribute constraints](#attribute-constraints) - ✏️ [Edit table](#edit-table) - [Basic actions](#basic-actions) - [Labeling and indexing](#labeling-and-indexing) - ▶️/⏹️ [Build table/Stop building table](#build-table) - 📑 [Duplicate](#duplicate) - 🗑 [Delete](#delete) ## Add a new attribute :::info Represented by the symbol ➕. ::: Adds a new attribute to the target table by opening the attribute creation window, shown below. ![Create attribute](/images/public-cloud/data-platform/product/lakehouse-manager/tables/picts/tables-new-attribute.png) ### Attribute constraints When setting an attribute on a table, you can add the following constraints: - **Required:** the field can never contain NULL. If a job tries to insert a null value into it, the query engine returns an error. - **Required + Identifier:** the field is required _and_ marked as an **identifier field**, meaning it is used to define the uniqueness of a row for **upsert** operations. See the [write strategy](https://docs.ovhcloud.com/pl/guides/public-cloud/data-platform/dpe-jobs-preferences.md#write-strategy) of the Load / Aggregate (Python and PySpark) actions for more information. ![Attribute constraints](/images/public-cloud/data-platform/product/lakehouse-manager/tables/picts/tables-attribute-constraints.png) :::warning **Once a table is built, you cannot add a Required field.** You can still _remove_ the Required property from an existing required field, but you cannot add the NOT NULL constraint to a field after the fact. The only way to add a required (or identifier) field to a built table is to fully rebuild it. See the [Rebuild action](https://docs.ovhcloud.com/pl/guides/public-cloud/data-platform/dpe-actions-rebuild.md). ::: :::info An identifier field cannot be a `double` or a `decimal`. ::: ## Edit table :::info Represented by the symbol ✏️. ::: Allows the editing of the table's schema and configuration. ![Edit table](/images/public-cloud/data-platform/product/lakehouse-manager/tables/picts/tables-config.png) ### Basic actions You can change the following basic configurations : - Name of the table - Table type - Table's description - Table tags (used to easily search for it) - Queryable (if a table isn't set as queryable, it won't be detected by the automated visual query builders of Analytics Manager and Lakehouse Manager Explorer) ### Labeling and Indexing When editing a table you can further add: - A **label** - One or several **partition keys/indexes** (_under advanced options_) ![MTA3](/images/public-cloud/data-platform/product/lakehouse-manager/tables/picts/tables-indexes.png) #### Labels You can choose one of the table’s attributes as an optional **label** for the primary key of this table. This turns the table into a _dictionary_ which is going to be stored in the cache of the [APIs](https://docs.ovhcloud.com/pl/guides/public-cloud/data-platform/landing-page-app-services-apis.md) that you deploy in your Project. The API will enforce the translation in the queries using this dictionary, and the label will automatically be displayed in your applications instead of the primary key. :::info **Pro Tip:** By defining labels, you don't have to store heavy additional data in aggregated tables. ::: #### Indexes Further, you can set **indexes** or **partition keys** to quickly locate data without having to search every row in a table. :::info **Pro tip:** Defining indexes improves the speed of data retrieval operations on a table at the cost of additional writes and storage space to maintain the index structure. ::: ## Build table :::info Represented by the symbol ▶️ if clicking to build, or ⏹️ if stopping build. ::: Click to start or stop build job for the target table. This job corresponds to physically building your tables in the database and is **required for loading and accessing your data** in the platform. Starting the build job will automatically open the job logs that you can monitor the job status: ![Tables4](/images/public-cloud/data-platform/product/lakehouse-manager/tables/picts/canvas-view-4.png) ## Duplicate :::info Represented by the symbol 📑. ::: Creates a copy of the target table that has to be built separately. ## Delete :::info Represented by the symbol 🗑. ::: Removes the target table from the logic data schema. Removes its physically built counterpart as well if the table has already been built. ## Go further If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/pl/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project. Ask questions, give your feedback and interact directly with the team building the Data Platform on the dedicated [Discord channel](https://discord.gg/ovhcloud). If you need support with your OVHcloud services, create a request in our [Help Centre](https://help.ovhcloud.com/csm?id=csm_get_help). Join our [community of users](https://community.ovhcloud.com/).