[HDDS-5374] [FSO] Handle rename and delete operation from an old client to a FSO bucket type

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Component/s: Ozone Manager
• Labels: pull-request-available
• Assignee: Rakesh Radhakrishnan
• Reporter: Aryan Gupta
• Created: 23/Jun/21 09:23
• Updated: 29/Apr/22 06:06
• Resolved: 29/Apr/22 06:06

Description

Suppose a new client creates a FSO type bucket and create set of files(for ex: /dir1/dir2/dir3/file-1, /dir1/dir2/dir3/file-2, /dir1/dir2/dir3/file-3, /dir1/dir2/dir3/file-4) into it.
Now old client(who hasn't upgraded to the newer version) should be able to perform rename/delete operations on the FSO type bucket created by the new client.
For ex:
#rename(/dir1/dir2, /dir1/newdir2)
#delete(/dir1).

Issue Links

• Dependent: HDDS-6223 Ozone 1.1.0 client listKeys on FSO bucket returns empty list
• relates to: HDDS-6040 [FSO] Support upgrade for the bucket layout
• links to: GitHub Pull Request #2764