Stavros Papadopoulos
Stavros Papadopoulos
Currently, TileDB's support for multi-range slicing is limited to cross products. We should be able to support any arbitrary set of subarray ranges to be submitted as a query. See...
This PR adds functionality for creating and executing a task graph. The functionality allows for tasks to dynamically generate sub task graphs while the graph is being executed. All internal...
This is to enable detecting corruption of the fragment metadata file during failed writes. This is the only case where a failed fragment will be "visible" by TileDB, despite its...
Currently we load all metadata of a fragment in main memory. For large arrays, the MBRs and other information about tiles may become a large memory issue, especially when multiple...
Our current algorithm operates on all array fragments to choose which subset to consolidate in the next step. A useful functionality would be to (i) tell the algorithm which subset...
We need a better way to handle deletion of fragments after consolidation, in the case where one fragment deletion fails. There are various options, e.g., removing only the fragment metadata...
Our consolidation algorithm deletes consolidated fragments. Due to the fact that S3 offers eventual consistency for object deletions, deleted consolidated fragments may still be "visible" for quite some time after...
Although it is not useful to set a zero-sized buffer to a read query, from a correctness standpoint it should still be doable. Also in case the result is empty...
For example `S3::is_bucket` just returns `false`, even when S3 is not supported.