i don't want to append or create a new array or explicitly delete the old array. just replace the array (with or without without time travel)

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

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.

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

Enable the use of TileDB from Rust.

"Currently, if your array consists of more than one attributes, TileDB requires you to provide values for all the attributes in each write operation." I'd love to be able to write attributes independently of each other.

Potentially integrate with Kerchunk to support ingesting mixed-shape arrays into a single xarray-dataset, as discussed here: https://forum.tiledb.com/t/dataset-with-mixed-shapes/485/4 Preferably with support for lazy-loading.

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 currently performs only slicing. It should allow other computations, such as filters, group-by queries and joins. This will help high-level application push compute closer to storage.