Conversation
sundapeng
force-pushed
the
storage-user-agent
branch
from
September 28, 2026 15:59
a51783a to
188f060
Compare
This was referenced Sep 28, 2026
sundapeng
changed the title
sundapeng
force-pushed
the
storage-user-agent
branch
from
September 29, 2026 01:08
188f060 to
a1912e5
Compare
Object storage requests went out without a User-Agent. Every opendal backend now sends Paimon's unified User-Agent format, module(transport;features) extended, by default paimon-rust/<version>(opendal/<version>). The parts come from the catalog options user-agent.module, user-agent.features and user-agent.extended, which REST requests share. For OSS, fs.oss.user.agent.module, fs.oss.user.agent.features and fs.oss.user.agent.extended override them part by part. dlf.access-tracking.extended-info is appended after the extended part.
sundapeng
force-pushed
the
storage-user-agent
branch
from
September 29, 2026 10:15
a1912e5 to
f99ff37
Compare
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
1 participant
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.
Purpose
Object storage requests from paimon-rust carry no
User-Agent, since neither opendal nor reqwest sets one, so this traffic can't be attributed in OSS access logs. The DLF access tracking info (dlf.access-tracking.extended-info) never reaches it either.This gives object storage requests Paimon's unified User-Agent format,
<module>(<transport>[;<feature>...])[ <extended>], which the REST client and the Java and Python clients adopt as well.Brief change log
paimon-rust/<version>(opendal/<version>), built from the catalog optionsuser-agent.module,user-agent.featuresanduser-agent.extended, which REST requests read too ([core] Unify the REST User-Agent format #992). Both versions are compile-time constants. The header is added in the shared HTTP transport, only when a request has none, after signing.fs.oss.user.agent.module/features/extendedoverride the matching part.dlf.access-tracking.extended-info, which DLF sends with the data token, is appended after the extended part.Examples:
paimon-rust/0.4.0(opendal/0.58.2)user-agent.features=Flink,user-agent.extended=vvrpaimon-rust/0.4.0(opendal/0.58.2;Flink) vvrfs.oss.user.agent.features=DataFusion, on a DLF catalog with access tracking enabledpaimon-rust/0.4.0(opendal/0.58.2;DataFusion) vvr tenantId/<uid> principalType/<type> userName/<name>Related: #992 (Rust REST), apache/paimon#10306 (Java OSS), apache/paimon#10307 (Python OSS).
Tests
io::unit tests: new cases for the shared options on every backend, the per-part OSS override and the tracking info, 1 of them against a local HTTP endpoint; 192 passed. Also checked on a live DLF catalog with access tracking enabled: the OSS access log shows the tracking info.cargo fmt --all -- --checkandcargo clippy --locked --all-targets --workspace --features fulltext,vortex -- -D warnings.API and Format
No.
Documentation
No.