Skip to content

fix: cache committed datatypes as a live hid_t, not a serialized buffer - #1

Closed
brtnfld wants to merge 1 commit into
masterfrom
revert-dtype-buffer-caching
Closed

fix: cache committed datatypes as a live hid_t, not a serialized buffer#1
brtnfld wants to merge 1 commit into
masterfrom
revert-dtype-buffer-caching

Conversation

@brtnfld

@brtnfld brtnfld commented Jul 6, 2026

Copy link
Copy Markdown
Owner

Summary

  • H5_daos_dtype_t now holds a live, open hid_t for its committed datatype again, matching how H5_daos_attr_t, H5_daos_dset_t, and H5_daos_map_t already cache their stored datatypes.
  • These IDs are legitimate app-level HDF5 IDs regardless of whether the connector treats them as internal bookkeeping, so H5Fget_obj_count(H5F_OBJ_ALL, ...) counting them is correct behavior, not something to avoid.

Test plan

  • Build against a real HDF5 + DAOS instance and confirm datatype commit/open/get/close and H5Ocopy of a committed datatype all still work
  • Confirm H5Fget_obj_count(H5F_OBJ_ALL, ...) includes open committed-datatype IDs as expected

H5_daos_dtype_t holds a live, open hid_t for its committed datatype,
matching how H5_daos_attr_t, H5_daos_dset_t, and H5_daos_map_t already
cache their stored datatypes. These IDs are legitimate app-level HDF5 IDs
regardless of whether a VOL connector considers them internal bookkeeping,
so H5Fget_obj_count(H5F_OBJ_ALL, ...) counting them is correct behavior,
not something to avoid.
@brtnfld

brtnfld commented Jul 6, 2026

Copy link
Copy Markdown
Owner Author

Folded into HDFGroup#73

@brtnfld brtnfld closed this Jul 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant