lokeshj1703 opened a new pull request, #19753: URL: https://github.com/apache/hudi/pull/19753
### Describe the issue this Pull Request addresses closes #19752 ### Summary and Changelog Adds `hoodie.filesystem.view.remote.response.charset` (default `ISO-8859-1`) so timeline-server HTTP responses can be decoded with a configured charset. Set it to `UTF-8` when partition or file paths contain non-ASCII characters. `TimelineServiceClient` and `HoodieTableServiceManagerClient` decode responses with the configured charset, and `EmbeddedTimelineService` propagates it into the remote view config. This is a fresh version of the stale #18121 against current master (the timeline client moved package to `org.apache.hudi.common.table.timeline`; commit 2 sets the config `sinceVersion` to the current release line). Testing note: `TestHoodieSparkSqlWriter.testUpsertWithUnicodePartitionPath` is added as a regression guard. It exercises an upsert over a Unicode partition through the embedded timeline server and passes on current master; I was not able to reproduce a failing (red) case for it locally with the in-process embedded server, so it guards behavior rather than proving the decode path is currently broken on master. Reviewers with more context on the timeline-server wire path may know a stronger repro. ### Impact Default behavior (ISO-8859-1) is a byte-preserving no-op versus the previous raw-stream handling, so existing deployments are unchanged. Deployments with non-ASCII paths can opt into UTF-8. ### Risk Level low. New opt-in config; default preserves existing behavior. ### Documentation Update New config `hoodie.filesystem.view.remote.response.charset` (documented via ConfigProperty). ### Contributor's checklist - [ ] Read through [contributor's guide](https://hudi.apache.org/contribute/how-to-contribute) - [ ] Enough context is provided in the sections above - [ ] Adequate tests were added if applicable -- 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]
