sundapeng opened a new pull request, #10306: URL: https://github.com/apache/paimon/pull/10306
### Purpose OSS requests from `paimon-oss` carry only the SDK's default User-Agent, `aliyun-sdk-java/3.17.4(Linux/...;<java>), Hadoop/3.3.4`, so Paimon traffic can't be told apart from other SDK traffic in OSS access logs. The DLF access tracking info (`dlf.access-tracking.extended-info`) that `JindoFileIO` appends to the User-Agent is also dropped on this path. `OSSFileIO` now builds `fs.oss.user.agent.prefix` in the layout Jindo uses, `module(transport;features) extended`, from the same `fs.oss.user.agent.module/features/extended` keys: - The module defaults to `Paimon/<version>` and the transport is `aliyun-sdk-java/<version>`. - The access tracking info is appended after any user-set extended value. - A user-set `fs.oss.user.agent.prefix` still takes precedence. For example: `Paimon/2.2-SNAPSHOT(aliyun-sdk-java/3.17.4;Flink) vvr uid/123, Hadoop/3.3.4`. ### Tests `OSSUserAgentTest`: 6 new cases, 1 of them against a fake OSS endpoint; 30 tests in `paimon-oss-impl` passed. -- 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]
