Open bkmartinjr opened 1 year ago
dense nd array - should the read operator support incremental/chunked reads, or should we remove the batch_size parameter? (the end user can still do their own chunking, as they know the chunk/result size)
We can support batching for dense arrays in the SOMA C++ API. This would remove the burden of batching from the user and provide a more symmetric API for dense and sparse arrays.
support batching for dense arrays in the SOMA C++ API.
Do you have a suggestion for what the interface would look like? I.e., a suggestion on how to return the coordinates of each chunk? I do think it would be useful
Tracking issue for tactical refinement of the abstract spec as we run up to an early pilot implementation.
get_version->'1.3.2-rc1-test+buildlabel'
) or as a numeric/label tuple/list (get_version -> [1, 3, 2, ['rc1', 'test'], ['build-label']]
)batch_size
parameter? (the end user can still do their own chunking, as they know the chunk/result size)shape
andreshape
- objectshape
is currently set at create-time. Some of the objects (eg, SOMA*NdArray) would benefit from a post-createreshape
operation. Should we support this, and what are the implications on implementation?