Symious

@adoroszlai Thanks for the review. Seems the config of "OZONE_OM_KEYNAME_CHARACTER_CHECK_ENABLED_KEY" will deny ``` * "\", "{", "}", "^", "", "#", "|", "%", "`", "[", "]", "~", "?" * and Non-printable...

Seems `Paths.get()` has been used in many places other than `RadixTree.getLongestPrefix()`.

@adoroszlai Thanks for revisiting this PR. I was wondering that this ticket is more than file encoding. As the test case shows, it can be triggered deliberately, a malicious user...

If there is a invalid character, it will always throw InvalidPathException if we use methods related to "Path". So are you suggesting that we should remove all the use of...

Sorry for the late reply. I tried to replace all the "Paths.get" with "String.split" and array oprerations, but I found some special cases with "~", ".", "..", which needs the...

I think it's normal when users are using OFS protocol.

@adoroszlai @ChenSammi Could you help to review this PR?

@JacksonYao287 Sure, thanks for the review. In https://github.com/apache/ozone/pull/2765#issuecomment-952091699, the concern I think is the misconfig of client side might trigger some dead loops, so an address was prefered to add...

@adoroszlai @avijayanhwx @ferhui Could you help to review this PR?

@avijayanhwx Could you help to check this issue? This issue can be a problem if we want to retrieve updated information from OM. In a small cluster, the connection from...