Currently, all array dimensions must be of the same type. TileDB should support dimensions of different types as well.

It would be cool to have the possibility to combine multiple tiledb arrays in a single logical view. A simple and fast way would be to require the same schema and just combine individual fragments s.t. the latest write wins. A more useful option would be to also allow concatenation of arrays along some dimension. In Dask, this could be exported as a single array with chunks aligned to the dataset borders. Even better, one could include filtering options or joining by keys. See also the discussion in https://github.com/TileDB-Inc/TileDB/issues/1475 .

TileDB should support attaching axes labels (dataframes in their full generality), so that the user can slice the array based on arbitrary axes label predicates.

TileDB does not allow arrays to change size. Appending new data and removing old data along a specific dimension (ex. time) is useful for realtime applications.

This will enable TileDB to support fast out-of-core key-value queries. In addition, it will be able support ND and prefix string queries.

Enable use of TileDB from Julia (www.julialang.org).

TileDB should support slicing with strides, which is quite common in numpy and similar tools.

Feature request from the forum: https://forum.tiledb.com/t/reducing-precision/137

Some processing on arrays (e.g., convolution) requires "tile overlaps". In other words, it is sometimes necessary to declare an array that consists of tiles which overlap certain amounts with one another. I think that TileDB would be better if the feature is supported.

Feature request in support of multi-array groups/collections: support the storage of metadata, a la Array.meta, on a group.