lokeshj1703 opened a new issue, #19752: URL: https://github.com/apache/hudi/issues/19752
### Problem When a Hudi table has partition or file paths containing non-ASCII (Unicode) characters, timeline-server HTTP responses can be decoded with the wrong charset. The fluent HTTP client's default handling can misinterpret UTF-8 bytes (for example the umlaut in a partition value like `München`) as Latin-1 during the response-to-path round-trip, which can lead to file-not-found style errors when a subsequent write reads existing data through the remote timeline server. There is no way to configure the charset used to decode timeline-server responses. ### Expected The charset used to decode timeline-server responses should be configurable, so deployments with non-ASCII partition or file paths can set UTF-8. ### Related A prior PR #18121 proposed the same change against an older master; it is stale. This tracks a fresh version against current master. ### Environment - Hudi version: master (1.x) - Remote timeline server with non-ASCII partition/file paths. -- 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]
