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.

Support array caching as described in this post: https://forum.tiledb.com/t/tiledb-cache-management/320 Several use case: Allow cache reuse between client sessions. Faster array metadata first byte. limit S3 egress cost Allow offline work or on bad connection with cached objects when prototyping Currently using minio gateway is a good workaround though so it might not be a high priority request.

Support array caching as described in this post: https://forum.tiledb.com/t/tiledb-cache-management/320 Several use case: Allow cache reuse between client sessions. Faster array metadata first byte. limit S3 egress cost Allow offline work or on bad connection with cached objects when prototyping Currently using minio gateway is a good workaround though so it might not be a high priority request.

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

It would be very helpful in certain cases to define custom structs / custom data types. Basically, support for Arrow structs would be the target: https://arrow.apache.org/docs/python/generated/pyarrow.struct.html Was also posted at https://forum.tiledb.com/t/how-to-store-a-vector-of-struct/172

Working on nested arrays is a crucial task in most scientific fields. I think TileDB could perfectly leverage its strengths to support the community working in that field: https://youtu.be/jvt4v2LTGK0?t=1366 Working with Data Management in TileDB and Data Wrangling in awkward-array ( https://github.com/scikit-hep/awkward-1.0 ) or other libraries with arrow support would be extremely beneficial workhorse. Any updates on when Arrow will be supported?

C# .NET is Open Source, cross platform, and widely used by many dev teams. It should be one of the supported languages for TileDB's API.

The user should be able to modify the array schema (e.g., add/remove attributes, change filters, tile capacity, etc) and time travel over the different versions.

Enable the use of TileDB from Rust.

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.