So far we explained that TileDB arrays and groups are stored as directories. There is no directory concept on GCS and other similar object stores. However, GCS uses character
/ in the object URIs which allows the same conceptual organization as a directory hierarchy in local storage. At a physical level, TileDB stores on GCS all the files it would create locally as objects. For instance, for array
gcs://bucket/path/to/array, TileDB creates array schema object
gcs://bucket/path/to/array/__array_schema.tdb, fragment metadata object
gcs://bucket/path/to/array/<fragment>/__fragment_metadata.tdb, and similarly all the other files/objects. Since there is no notion of a “directory” on GCS, nothing special is persisted on GCS for directories, e.g.,
gcs://bucket/path/to/array/<fragment>/ does not exist as an object.