[HDFS-17263] RBF: Fix client ls trash path cannot get except default nameservices trash path

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.0
• Fix Version/s: 3.4.0
• Component/s: rbf
• Labels: pull-request-available
• Target Version/s: 3.4.0
• Hadoop Flags: Reviewed
• Assignee: liuguanghua
• Reporter: liuguanghua
• Created: 22/Nov/23 08:16
• Updated: 28/Jan/24 01:11
• Resolved: 30/Nov/23 14:48

Description

With  HDFS-16024, we can rename data to the Trash should be based on src locations. That is great for my useage.  After a period of use, I found this cause a issue.

There are two nameservices ns0   ns1,  and ns0 is the default nameservice.

(1) Add moutTable 

/home/data -> (ns0, /home/data)

/data1/test1 -> (ns1, /data1/test1 )

/data2/test2 -> (ns1, /data2/test2 )

(2)mv file to trash

ns0:   /user/test-user/.Trash/Current/home/data/file1

ns1:   /user/test-user/.Trash/Current/data1/test1/file1

(3) client via DFSRouter  ls will not see  /user/test-user/.Trash/Current/data1

(4) client ls  /user/test-user/.Trash/Current/data2/test2 will return exception .

 

 

Issue Links

• links to: GitHub Pull Request #6291