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
Motivation
We have currently no way to determine if a physical file is an orphan, that is to say it has not been registered in Nexus.
With the new ways to register files (delegation, presigned urls), where the client plays a most important role, this is most likely to happen.
Storing files in S3 having a cost, identifying those orphans will be useful.
Adding the location in the fields in event metrics will allow to use it as a reverse index and find if any file event is associated with this location.
Not in scope
The tool allowing to identify orphans will be part of another ticket
An endpoint to find the Nexus files from the location
The text was updated successfully, but these errors were encountered:
Motivation
We have currently no way to determine if a physical file is an orphan, that is to say it has not been registered in Nexus.
With the new ways to register files (delegation, presigned urls), where the client plays a most important role, this is most likely to happen.
Storing files in S3 having a cost, identifying those orphans will be useful.
Adding the location in the fields in event metrics will allow to use it as a reverse index and find if any file event is associated with this location.
Not in scope
The text was updated successfully, but these errors were encountered: