sundapeng opened a new pull request, #991: URL: https://github.com/apache/paimon-rust/pull/991
### Purpose Object storage requests from paimon-rust carry no `User-Agent` at all. 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`) that Java's `JindoFileIO` appends to the User-Agent is also dropped. This follows the layout JindoSDK uses, `module(transport;features) extended`, the same as the Java and Python changes in apache/paimon#10306 and apache/paimon#10307. ### Brief change log - Every opendal backend sends `paimon-rust/<version>(opendal/<version>)`. The header is added in the shared HTTP transport, only when a request has none, and after signing. - OSS also reads `fs.oss.user.agent.module`, `fs.oss.user.agent.features` and `fs.oss.user.agent.extended`. `dlf.access-tracking.extended-info` is appended after any user-set extended value, for example `paimon-rust/0.4.0(opendal/0.58.2;DataFusion) vvr uid/123`. ### Tests - `io::user_agent` and `io::storage_oss`: 9 new cases, 1 of them against a local HTTP endpoint; 16 passed. - `cargo fmt --all -- --check` and `cargo clippy --locked --all-targets --workspace --features fulltext,vortex -- -D warnings`. ### API and Format No. ### Documentation No. -- 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]
