You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
If pbcore for a guid that doesn't already exist in AMS2 is accidentally put through instantiation reset ingester, there is a vague error thrown STATUS: 500 javax.jcr.RepositoryException: org.modeshape.jcr.value.binary.BinaryStoreException: Unable to find binary value with key "bc55d5f718cb5f5ed4665ffba561657a5a26e1cc" within binary store at "/mnt/sdf/fedora-data/fcrepo.binary.directory"
However, a record is still made , but runs into an error when trying to go to it.
To Reproduce
Steps to reproduce the behavior:
Try to enter pbcore for a non-existent guid in AMS2 into the instantiation reset ingester
See error
Search the guid in AMS2
See record and subsequent error when you try to go to it.
Expected behavior
Nothing is ingested and a clear error is reported during ingest step
Additional context
I thought maybe I could resend it through the instantiation reset, because technically it did create a record for the guid, but I got the same error
The text was updated successfully, but these errors were encountered:
Describe the bug
If pbcore for a guid that doesn't already exist in AMS2 is accidentally put through instantiation reset ingester, there is a vague error thrown
STATUS: 500 javax.jcr.RepositoryException: org.modeshape.jcr.value.binary.BinaryStoreException: Unable to find binary value with key "bc55d5f718cb5f5ed4665ffba561657a5a26e1cc" within binary store at "/mnt/sdf/fedora-data/fcrepo.binary.directory"
However, a record is still made , but runs into an error when trying to go to it.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Nothing is ingested and a clear error is reported during ingest step
Additional context
I thought maybe I could resend it through the instantiation reset, because technically it did create a record for the guid, but I got the same error
The text was updated successfully, but these errors were encountered: