Closed taojing2002 closed 3 months ago
After discussing with Jing, it appears that in the described situation above, the client (Metacat) had not attempted to store any metadata. This explains why no subdirectories exist under /metadata
. There already exists a junit test which covers this potential issue - so no action is needed at this time. I am closing this issue and will* re-open if we see this behaviour with further testing.
When some bad things happen, and Metacat tries to erase both the object and system metadata from HashStore, it calls
deleteObject
anddeleteMetadata
. It turns out that thedeleteObject
method keep the directory structure but delete the object file even though the directory is empty. But thedeleteMetadata
method will delete both directories and system metadata file. So the directory structure looks like: