# CreateTableRequest
## Properties
Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**identity** | Option<[**models::Identity**](Identity.md)> | | [optional]
**context** | Option<**std::collections::HashMap<String, String>**> | Arbitrary context for a request as key-value pairs. How to use the context is custom to the specific implementation. REST NAMESPACE ONLY Context entries are passed via HTTP headers using the naming convention `x-lance-ctx-<key>: <value>`. For example, a context entry `{\"trace_id\": \"abc123\"}` would be sent as the header `x-lance-ctx-trace_id: abc123`. | [optional]
**id** | Option<**Vec<String>**> | | [optional]
**mode** | Option<**String**> | There are three modes when trying to create a table, to differentiate the behavior when a table of the same name already exists. Case insensitive, supports both PascalCase and snake_case. Valid values are: * Create: the operation fails with 409. * ExistOk: the operation succeeds and the existing table is kept. * Overwrite: the existing table is dropped and a new table with this name is created. | [optional]
**properties** | Option<**std::collections::HashMap<String, String>**> | Business logic properties stored and managed by the namespace implementation outside Lance context, if supported by the implementation. | [optional]
**storage_options** | Option<**std::collections::HashMap<String, String>**> | Storage options that configure overrides for writing table data and metadata during table creation. These are passed to Lance for the write path. | [optional]
[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)