On Wed, Dec 13, 2023 at 10:57:10AM +0100, Rok Jaklič wrote:
Hi,
shouldn't etag of a "parent" object change when "child" objects are added on s3?
Example: 1. I add an object to test bucket: "example/" - size 0 "example/" has an etag XYZ1 2. I add an object to test bucket: "example/test1.txt" - size 12 "example/test1.txt" has an etag XYZ2 "example/" has an etag XYZ1 ... should this change?
I understand that object storage is not hierarchical by design and objects are "not connected" by some other means than the bucket name. If you understand the storage is not hierarchical, why do you think one object is a parent of the other (child) object?
In your example, there are 2 objects: "example/" "example/test1.txt" The "/" in the name is not special in any way. It would still be 2 objects if the object names were: "exampleZ" "exampleZtest1.txt" I want to understand why you (and others) feel that one object is the parent the other child object. -- Robin Hugh Johnson Gentoo Linux: Dev, Infra Lead, Foundation President & Treasurer E-Mail : robbat2@gentoo.org GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136