ivandika3 commented on PR #8063: URL: https://github.com/apache/hadoop/pull/8063#issuecomment-3539600419
@ayushtkn Thanks for taking a look. > curious where we will use it The problem that we encountered is that we have a client that can access both hdfs:// and ofs:// but TrashPolicyDefault and OzoneTrashPolicy is not compatible (TrashPolicyDefault was changed that cause issues where applied to Ozone). Despite setting "fs.trash.classname" in both HDFS and Ozone, only one will be picked (usually TrashPolicyDefault) which causes user not being able to move files to trash in Ozone. Other related works like HADOOP-18013 and HADOOP-18893 approached it by using per-scheme configuration (e.g. fs.s3a.trash.classname) > adding this as a FileSystem API looks overkill to me, if it required for some particular use case, maybe part of getServerDefaults()? I am not aware with `getServerDefaults` and it seems we can move the TrashPolicy as part of `getServerDefaults` too. However, I feel adding a new FileSystem API is more explicit which also allows us to specify its behavior in FileSystem.md. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
