Description of problem: If the object is modified but it is the same object, do not generate a new version. Just discard the operation or update metadata: -With simple uploads, if the ETag header is the same: -Option 1: Discard the operation. -Option 2: Update only metadata (i.e: LastModified field) but not the object content itself. -With multipart uploads, if the ETag header of the final object is the same: -Option 1: Discard the operation. -Option 2: Update only metadata (i.e: LastModified field) but not the object content itself. -Partial uploads should be deleted to free up space in the RGW archive zone and clean up orphaned RADOS objects. -Some advantages of implementing this feature: -With the current behaviour, a user could upload the same object many times and totally fill up the RGW archive zone Ceph cluster. -If the ETag header check is done prior transferring the object and the operation is discarded, resource usage (network bandwidth, CPU, Memory, ...) will be reduced.
Issue relevant to RGW archive zone.
What's the status of this BZ?
(In reply to Yaniv Kaul from comment #8) > What's the status of this BZ? This might need to be considered for a later release, as we are yet to find an acceptable solution. Checking/comparing checksums of large number of object versions will involve an undesirable linear time complexity, unless we plan to cap the number of versions an object can have.
*** Bug 2210132 has been marked as a duplicate of this bug. ***
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days