Repository navigation
[io] Propagate User-Agent options to Jindo OSS - #1116
Merged
Merged
Conversation
JingsongLi
approved these changes
Oct 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Jindo OSS reads ignore catalog
user-agent.*and overwrite custom features, so their HTTP User-Agent loses the application's identity. Map the common options to Jindo's OSS keys while preserving OSS-specific overrides,paimon-rust, and DLF access-tracking text.Tests: 12 Jindo unit tests; real Jindo SDK against a local OSS mock with the HTTP User-Agent asserted; real pre DLF PyPaimon→Rust read (
native_planned=True). OSS access logs from that read show 6GetObject206 and 6GetObjectMeta200 requests for manifests with the expected custom UA. The Parquet data read used PyPaimon's separate AWS C++ backend.