TileDB Core

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 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.

Enable the use of TileDB from Rust.

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

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.

"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.

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?

The user should be able to delete any number of cells. Currently this is possible via directly inserting "tombstones", but the deletion logic fall on the higher-level application. TileDB should be able to natively support deletions.