devabhishekpal commented on PR #9793: URL: https://github.com/apache/ozone/pull/9793#issuecomment-3976781746
> The / separator partially fixes the problem, but the mixed encoding scheme of UTF-8 and big-endian long serialization still means we may have conflicts. The 2f byte could also occur in the long section of the key. If we just find the first 2f byte this would still work, but I think it would be better to use one uniform encoding scheme for the whole key. I'm thinking we could still convert the long to a big endian byte array for fixed length, but UTF-8 encode it with the rest of the key. This is similar to the FSO keys, which still UTF-8 encode their parent object IDs. @errose28 do you mean: - `partNumber` -> `big-endian bytes` -> `hex/base64` string - key = `uploadId` + "/" + `encodedPartBytes` from above transition And then we UTF-8 encode it? -- 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]
