Stavros Papadopoulos

@gatesn we partially addressed this issue in https://github.com/TileDB-Inc/TileDB/pull/2361, but the appropriate fix here is to indicate for a dimension that there is no tile extent at all. That requires a...

Definitely in our roadmap :)! Please tell us more about your data interests and typical workflows.

Hi @olszewskip, thanks for reaching out! Regarding VCF data, have you checked https://github.com/TileDB-Inc/TileDB-VCF? We are quite actively developing it. Regarding representing graph data as sparse adjacency matrices, this is of...

Hi @ryan-salo, we will soon publish several tutorials on tweaking the TileDB compression for LAZ data. The current defaults are not appropriate, we are fixing those in the next imminent...

Hi @ryan-salo, it probably will for the case of X, Y and Z. Please stay tuned though, we are working on another compressor that will improve even further the pointcloud...

TileDB does not currently support any kind of array schema alteration. This is in our roadmap, being tracked here: https://feedback.tiledb.com/tiledb-core/p/schema-evolution We will try to add this feature very soon.

Thanks @RaananHadar! I am actually refactoring the docs as we speak, so I'll consider your suggestion here.

@gatesn this is already in our roadmap, along with dictionary compression, RLE compression for strings and min/max values for attribute tiles. We hope to implement those soon.

Thanks Nick, this is a known issue with empty string coordinate strings that we are fixing.

Here is what could happen: * If the two tiledb processes are both reading, both writing, or one reading and one writing, then there is no issue (no locking is...