sundapeng opened a new pull request, #992: URL: https://github.com/apache/paimon-rust/pull/992
### Purpose REST catalog requests from paimon-rust carry no `User-Agent`, since reqwest sets none by default, so these clients can't be attributed in the catalog server's request logs. REST requests now carry Paimon's unified User-Agent format, `<module>(<transport>[;<feature>...])[ <extended>]`, the one the object storage requests adopt as well. ### Brief change log - The REST client and the DLF ECS token client send `paimon-rust/<version>(reqwest)`. The version is a compile-time constant. - A user-set `header.User-Agent` option still takes precedence and is the only User-Agent sent. Examples, captured on a local endpoint: | Client | User-Agent | |---|---| | REST catalog | `paimon-rust/0.4.0(reqwest)` | | REST catalog with `header.User-Agent=starrocks/user` | `starrocks/user` | | DLF ECS token loader | `paimon-rust/0.4.0(reqwest)` | Related: #991 (object storage User-Agent), apache/paimon#10308 (Java REST), apache/paimon#10309 (Python REST). ### Tests - `api::rest_client` and `api::auth::dlf_provider`: 3 new cases against a local HTTP endpoint; `cargo test -p paimon --lib -- api::` passed (90). - `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]
