HDF read fails if creation order is not tracked about cgns HOT 5 CLOSED

By the way, does anyone know the tool to use to see if creation order is or not tracked for a given hdf file ? hdfview reports this information but I did not find the equivalent command line tool to use.

from cgns.

From my understanding there was a change in CGNS MLL implementation around 3.x release requiring to have INDEX_CRT_ORDER by default. Thus recent hdf5 file should not use the INDEX_NAME.
But, in develop version of CGNS/MLL a change was recently added to detected if the whole file use CRT_ORDER or not and then read the old 2.5 files. It is possible that some bug or incompability are still present.

What is the usecase that use H5_INDEX_NAME ?

@brtnfld any comments ?

from cgns.

You are correct; this oversight was fixed in PR #690 to develop.

Can you try it with develop and see if you still have an issue? I might have missed an H5Literate correction.

There's no hdf5 tool that displays the creation order. However, you can in h5dump the sort between descending and ascending to see if it changes anything.

The easiest is to create an HDF5 program to open the root group and use H5Pget_link_creation_order to get it explicitly.

from cgns.

@brtnfld I just built the library using develop branch and the problem is gone. Thanks for the PR !

@MicK7 We used to write hdf files using our own tools instead of MLL implementation, that is why we have name indexed files.
We are going to change these tools to save the CRT_ORDER, but as I said above maybe this should be stated somewhere in the docs ? I also add a similar issue concerning misleading documentation few mounths ago : #678.

from cgns.

Closing, feel free to open again. You should not need to save the CRT_ORDER.

from cgns.