VDS Relative Path

Hdf-forum archives
1

Hi,

I saw in the 1.10.0-patch1 release notes that:

- VDS feature limitation
Currently, the path to a VDS source file is interpreted as relative to
the directory where the executable program runs and not to the HDF5 file
with the VDS dataset unless a full path to the source file is specified
during the mapping.

Will this restriction be relaxed in the near future? We often access
data from programs executed in different directories than the HDF5
datasets (where the main VDS file resides). When creating the VDS file,
we use relative paths to form the mapping for portability.

Thanks,
Matthew

2

Hi Matthew,

Yes, we plan to address this limitation in the HDF5 1.10 release (1.10.2) that will be done by the end of the year.

Elena

···

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Elena Pourmal The HDF Group http://hdfgroup.org
1800 So. Oak St., Suite 203, Champaign IL 61820
217.531.6112
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

On Jun 6, 2016, at 8:10 AM, Matthew Clay <mpclay@gmail.com<mailto:mpclay@gmail.com>> wrote:

Hi,

I saw in the 1.10.0-patch1 release notes that:

- VDS feature limitation
Currently, the path to a VDS source file is interpreted as relative to
the directory where the executable program runs and not to the HDF5 file
with the VDS dataset unless a full path to the source file is specified
during the mapping.

Will this restriction be relaxed in the near future? We often access
data from programs executed in different directories than the HDF5
datasets (where the main VDS file resides). When creating the VDS file,
we use relative paths to form the mapping for portability.

Thanks,
Matthew

_______________________________________________
Hdf-forum is for HDF software users discussion.
Hdf-forum@lists.hdfgroup.org<mailto:Hdf-forum@lists.hdfgroup.org>
http://lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org
Twitter: https://twitter.com/hdf5

3

Dear Elena,

I hope you are well. Sorry to reopen this thread, but I just wanted to check to see if the VDS limitation we previously discussed is still on track to be addressed in 1.10.2.

Thank you and The HDF Group for this feature, but it would be great if we could tell HDF5 "please interpret the links in the VDS as being relative to the VDS file, not the executable reading the file."

Thanks again.

Best,
Matthew

···

On 06/06/2016 10:17 AM, Elena Pourmal wrote:

Hi Matthew,

Yes, we plan to address this limitation in the HDF5 1.10 release (1.10.2) that will be done by the end of the year.

Elena

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Elena Pourmal The HDF Group http://hdfgroup.org
1800 So. Oak St., Suite 203, Champaign IL 61820
217.531.6112
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

On Jun 6, 2016, at 8:10 AM, Matthew Clay <mpclay@gmail.com > <mailto:mpclay@gmail.com>> wrote:

Hi,

I saw in the 1.10.0-patch1 release notes that:

- VDS feature limitation
Currently, the path to a VDS source file is interpreted as relative to
the directory where the executable program runs and not to the HDF5 file
with the VDS dataset unless a full path to the source file is specified
during the mapping.

Will this restriction be relaxed in the near future? We often access
data from programs executed in different directories than the HDF5
datasets (where the main VDS file resides). When creating the VDS file,
we use relative paths to form the mapping for portability.

Thanks,
Matthew

_______________________________________________
Hdf-forum is for HDF software users discussion.
Hdf-forum@lists.hdfgroup.org <mailto:Hdf-forum@lists.hdfgroup.org>
http://lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org
Twitter: https://twitter.com/hdf5

_______________________________________________
Hdf-forum is for HDF software users discussion.
Hdf-forum@lists.hdfgroup.org
http://lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org
Twitter: https://twitter.com/hdf5

4

Dear Matthew and All,

I apologize for my slow response.

Dear Elena,

I hope you are well.

Well...ignoring emails is not a good sign :slight_smile:

Sorry to reopen this thread, but I just wanted to
check to see if the VDS limitation we previously discussed is still on
track to be addressed in 1.10.2.

Yes, we do want to fix it in 1.10.2.

Thank you and The HDF Group for this feature, but it would be great if
we could tell HDF5 "please interpret the links in the VDS as being
relative to the VDS file, not the executable reading the file."

We were also thinking to provide an option to specify a path to source file(s) via environment variable and using an API.

Please let me know if the proposed fixes will cover your use cases.

Thank you!

Elena

···

On Jun 16, 2017, at 8:13 AM, Matthew Clay <mpclay@gmail.com> wrote:

Thanks again.

Best,
Matthew

On 06/06/2016 10:17 AM, Elena Pourmal wrote:

Hi Matthew,

Yes, we plan to address this limitation in the HDF5 1.10 release
(1.10.2) that will be done by the end of the year.

Elena

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Elena Pourmal The HDF Group http://hdfgroup.org
1800 So. Oak St., Suite 203, Champaign IL 61820
217.531.6112
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

On Jun 6, 2016, at 8:10 AM, Matthew Clay <mpclay@gmail.com >> <mailto:mpclay@gmail.com>> wrote:

Hi,

I saw in the 1.10.0-patch1 release notes that:

- VDS feature limitation
Currently, the path to a VDS source file is interpreted as relative to
the directory where the executable program runs and not to the HDF5 file
with the VDS dataset unless a full path to the source file is specified
during the mapping.

Will this restriction be relaxed in the near future? We often access
data from programs executed in different directories than the HDF5
datasets (where the main VDS file resides). When creating the VDS file,
we use relative paths to form the mapping for portability.

Thanks,
Matthew

_______________________________________________
Hdf-forum is for HDF software users discussion.
Hdf-forum@lists.hdfgroup.org <mailto:Hdf-forum@lists.hdfgroup.org>
http://lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org
Twitter: https://twitter.com/hdf5

_______________________________________________
Hdf-forum is for HDF software users discussion.
Hdf-forum@lists.hdfgroup.org
http://lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org
Twitter: https://twitter.com/hdf5

_______________________________________________
Hdf-forum is for HDF software users discussion.
Hdf-forum@lists.hdfgroup.org
http://lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org
Twitter: https://twitter.com/hdf5

5

Dear Elena,

It is great to hear that it might be fixed in 1.10.2. For me, something in the API like a file access property list would be great. Thank you very much for your help.

Best,
Matthew

···

On 07/17/2017 07:59 PM, Elena Pourmal wrote:

Dear Matthew and All,

I apologize for my slow response.

On Jun 16, 2017, at 8:13 AM, Matthew Clay <mpclay@gmail.com> wrote:

Dear Elena,

I hope you are well.

Well...ignoring emails is not a good sign :slight_smile:

Sorry to reopen this thread, but I just wanted to
check to see if the VDS limitation we previously discussed is still on
track to be addressed in 1.10.2.

Yes, we do want to fix it in 1.10.2.

Thank you and The HDF Group for this feature, but it would be great if
we could tell HDF5 "please interpret the links in the VDS as being
relative to the VDS file, not the executable reading the file."

We were also thinking to provide an option to specify a path to source file(s) via environment variable and using an API.

Please let me know if the proposed fixes will cover your use cases.

Thank you!

Elena

Thanks again.

Best,
Matthew

On 06/06/2016 10:17 AM, Elena Pourmal wrote:

Hi Matthew,

Yes, we plan to address this limitation in the HDF5 1.10 release
(1.10.2) that will be done by the end of the year.

Elena

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Elena Pourmal The HDF Group http://hdfgroup.org
1800 So. Oak St., Suite 203, Champaign IL 61820
217.531.6112
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

On Jun 6, 2016, at 8:10 AM, Matthew Clay <mpclay@gmail.com >>> <mailto:mpclay@gmail.com>> wrote:

Hi,

I saw in the 1.10.0-patch1 release notes that:

- VDS feature limitation
Currently, the path to a VDS source file is interpreted as relative to
the directory where the executable program runs and not to the HDF5 file
with the VDS dataset unless a full path to the source file is specified
during the mapping.

Will this restriction be relaxed in the near future? We often access
data from programs executed in different directories than the HDF5
datasets (where the main VDS file resides). When creating the VDS file,
we use relative paths to form the mapping for portability.

Thanks,
Matthew

_______________________________________________
Hdf-forum is for HDF software users discussion.
Hdf-forum@lists.hdfgroup.org <mailto:Hdf-forum@lists.hdfgroup.org>
http://lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org
Twitter: https://twitter.com/hdf5

_______________________________________________
Hdf-forum is for HDF software users discussion.
Hdf-forum@lists.hdfgroup.org
http://lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org
Twitter: https://twitter.com/hdf5

_______________________________________________
Hdf-forum is for HDF software users discussion.
Hdf-forum@lists.hdfgroup.org
http://lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org
Twitter: https://twitter.com/hdf5

_______________________________________________
Hdf-forum is for HDF software users discussion.
Hdf-forum@lists.hdfgroup.org
http://lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org
Twitter: https://twitter.com/hdf5