[#231] Fix get latest version node #231

Merged

alexvanin merged 1 commits from :feature/fix_get_latest_node_version into support/v0.28

2023-10-06 09:26:40 +00:00

r.loginov commented

2023-10-06 08:01:55 +00:00

Collaborator

This happens because when requesting a tree service to get a node of the object version, we get a node that is a secondary object a. The resulting node does not have an OID attribute, and as a result, further deletion of the object with the a key does not occur.

As a solution, an option is proposed in which we get the entire list of nodes by a certain path (key) and then choose the node of the object version we need ourselves, depending on the presence of the OID attribute and the timestamp value.

Signed-off-by: Roman Loginov r.loginov@yadro.com

We have the following problem. For example, if we created an object with the key a and an object with the key a/b (it is important that the name of the "folder" is the same as the name of the object), and then we call the aws rm --recursive command to the bucket in which they lie, then in the end the object with the key a it is not deleted. This happens because when requesting a tree service to get a node of the object version, we get a node that is a secondary object a. The resulting node does not have an OID attribute, and as a result, further deletion of the object with the a key does not occur. As a solution, an option is proposed in which we get the entire list of nodes by a certain path (key) and then choose the node of the object version we need ourselves, depending on the presence of the OID attribute and the timestamp value. Signed-off-by: Roman Loginov <r.loginov@yadro.com>