-
Notifications
You must be signed in to change notification settings - Fork 38
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
Incorrect domains on external links #22
Comments
I've implemented some fixes for this in h5serv - please update your h5serv repo and try it out. There are a bunch of edge cases, but I think this should be good for common usage. |
It works, although it is tripped up if the external file has a different extension than the default server extension. In my example, the file
So the non-default extension,
|
There seems to be another problem. If a group contains an externally linked dataset and I call the group's
|
Ah, looks like I did the transform for the link operation, but not the links one. |
The |
Good. I'll close this one then. |
We have an h5serv server running, and loading regular HDF5 files works well. However, if the file contains an external link, it cannot access the external file because the file path is not converted to a valid domain.
Here's some output when accessing a file with path
mullite/mullite_300K.nxs
with respect to the h5serv datapath, with the root domain name ofexfac
(the config file sets the file extension to be.nxs
on this server):Presumably, h5pyd should convert the external file path to a valid domain string. In this case, the file path is relative to the parent HDF5 file - I'm not sure what a correct domain name would be if the file path was absolute.
The text was updated successfully, but these errors were encountered: