-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fragment index argument refers to C++ array (starts at 0) #515
Comments
Thanks for taking the time to file an issue. What is described here is correct -- and intentional. The R package wraps the TileDB Core API, and adheres to its interface. As this API uses zero-based indexing, so does the R interface to it. |
Thanks for your prompt reply! From R perspective, a user doesn't expect zero-based indexing but since it is intentional there is no problem - as long as it is documented somewhere; apologies if I missed it. |
To return a fragment info value for a given index, the fragment index argument
fid
expects the index to start at 0. For example, if you'ven
fragments, you need to passn-1
to get the information for then
fragment. This relates to functions liketiledb_fragment_info_get_timestamp_range(object, fid)
,tiledb_fragment_info_get_timestamp_range(finfo, fid)
etc.The following example shows how the issue came up initially.
Session info
The text was updated successfully, but these errors were encountered: