NSFS | Versioning | Implement GET/HEAD object

Is your feature request related to a problem? Please describe. This feature is part of NSFS versioning.

Describe the solution you’d like GET object will return the latest or the requested version object. Basically bucket can be version:

1. Disabled

• No call flow will/behaviour will be changed

1. Enabled

• return the latest object if specific version is not requested.
• fetch the stat of all objects and return the object which is requested for

1. Suspended Same behaviour as in case of Version enabled

steps:

1. Funnel the application to namespaceFS.js based on bucketspace and namespace
2. if version is specified as part of the GET, then stat(“version”) under .versiondirectory,

  if present  
        return the file 
  else 
         return err

1. If no version specified then return the file under the specified path
2. Follow the same process for HEAD object, instead of data just return the metadata of the request file

@dannyzaken @romayalon Please correct if wrong

[romayalon]

https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListObjectVersions.html So actually the default behavior of list-object-versions is to return all the bucket versions, The user can pass parameters to filter the result on the server side. Always continue thinking, I appreciate it!

[romayalon]

Hi @v-harihar @guymguym back with an answer from the FS experts, The suggestion of creating directories for each object, and maintaining them can be more expensive in time and in place. think about a situation where we have millions of objects… And regarding list object versions - maybe i’m mistaken but I believe that one readdir operation on .versions/ should take less time than millions of readdir operations (when having millions of objects each has a directory under .versions/)

I suggested to the GPFS team to add a prefix field for readdir, which seems to be possible if really needed