Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Creating a dimension requires specifying a name, the dimension datatype, the dimension domain and the space tile extent. Below you can see an example of creating an int32
dimension called dim
with domain [1,4]
, and tile extent 2
.
Supported Dimension Datatypes:
The following values are members of the TileDB.CSharp.DataType
enum:
Dimensions accept filters such as compressors. This is described in detail here.
After creating some dimensions, you can create the array domain as follows:
The order of the dimensions as added to the domain is important later when slicing subarrays. Remember to give priority to more selective dimensions, in order to maximize the pruning power during slicing.
When creating the domain, the dimension names must be unique.
Creating an attribute requires specifying a (optional; attribute names starting with __
are reserved) name and a (required) datatype. In the example below we create an int32
attribute called attr
.
An attribute can also store a fixed number of values (of the same datatype) in a single cell, or a variable number of values. You can specify this as follows:
An attribute may also be nullable. This allows designating each cell as valid or null. Applicable to both fixed-sized and var-sized attributes.
Note: nullable Python attributes should be used with the from_pandas
API or Pandas series with a Pandas extension dtype (e.g. StringDtype
).
Supported Attribute Datatypes:
Crossed data types are deprecated.
For fixed-sized attributes, the input fill value size should be equal to the cell size.
Datatype | Description | Array Type |
---|---|---|
Datatype | Description | Array Type | Internal TILEDB Datatype Mapping |
---|---|---|---|
Datatype | Description | Array Type |
---|---|---|
Datatype | Description | Array Type |
---|---|---|
Datatype | Description |
---|
Datatype | Description | Internal TILEDB Datatype Mapping |
---|
Datatype | Description |
---|
Attributes accept filters such as compressors. This is described in detail .
There are situations where you may read "empty spaces" from TileDB arrays. For those empty spaces, a read query will return some for the selected attributes. You can set your own fill values for these cases as follows:
A call to setting the number of cells for an attribute (see above) sets the fill value of the attribute to its . Therefore, make sure you set the fill values after deciding on the number of values this attribute will hold in each cell.