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
In version 2 of Clowder we will be implementing file versioning from the beginning. Since we will be leveraging Minio and S3 it makes sense to build our implementation around object versioning in those systems. Here is some information on how Minio manages versioned buckets:
When asking for a file without specifying the versionId, the latest version is returned (we should mirror this behavior)
Some questions:
Since the file id in Minio will be the file id in Mongo, do we need to keep the versions ids in Mongo, or retrieve them from Minio? This might be relevant to the discussion of keeping metadata attached to specific versions. This means that the versionId would need to be captured by Clowder to be used internally.
The text was updated successfully, but these errors were encountered:
Some metadata should be version-specific (previews, metadata, tags, etc...), some metadata should be global and not change with versions (name, description).
In version 2 of Clowder we will be implementing file versioning from the beginning. Since we will be leveraging Minio and S3 it makes sense to build our implementation around object versioning in those systems. Here is some information on how Minio manages versioned buckets:
https://docs.min.io/docs/minio-bucket-versioning-guide.html
A couple things to note:
versionId
, the latest version is returned (we should mirror this behavior)Some questions:
versionId
would need to be captured by Clowder to be used internally.The text was updated successfully, but these errors were encountered: