-
-
Notifications
You must be signed in to change notification settings - Fork 265
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
h5dump doesn't honor HDF5_VOL_CONNECTOR
.
#2645
Comments
H5dump doesn't need to do anything about the environment variable. That's the entire point of the environment variable. |
To be clear, when the HDF5_VOL_CONNECTOR environment variable is set, it replaces the default VOL connector on File Access Property Lists. Therefore, h5dump doesn't need to pay attention to use_custom_vol_g because it doesn't need to setup a custom File Access Property List. It will just use the default one pointed to by H5P_DEFAULT which will already have the VOL set on it. |
I just want to see a consistent behavior from the end-user's perspective. |
When it eventually gets down to opening the file, yes both the command-line option and setting the environment variable are supposed to function the same way by just loading the DAOS VOL. If they do not function the same way, it's almost certainly a bug in the tools, but make sure you have a clean environment when testing that. Also, |
HDF5_VOL_CONNECTOR
.HDF5_VOL_CONNECTOR
.
Not a bug - closing. |
Describe the bug
h5dump behaves differently when
HDF5_VOL_CONNECTOR=daos
environment variable--vol-name=daos
Expected behavior
Same behavior.
Platform (please complete the following information)
Additional context
Add any other context about the problem here.
The
use_custom_vol_g
is only active when--vol-name
option is provided.The text was updated successfully, but these errors were encountered: