JingsongLi opened a new pull request, #244:
URL: https://github.com/apache/paimon-cpp/pull/244

   ### Purpose
   
   Linked issue: N/A
   
   Add Java-compatible DLF authentication to the REST Catalog:
   
   - Support DLF4-HMAC-SHA256 and DlfNext OpenAPI HMAC-SHA1 request signing.
   - Support static AK/SK/STS credentials, refreshable local token files, and 
ECS RAM role credentials.
   - Match Java credential precedence, endpoint-based signer selection, token 
parsing, and one-hour refresh window.
   - Disable automatic redirects for DLF-signed requests to prevent STS header 
leakage and invalid redirected signatures.
   - Apply the Java-compatible three-minute timeout to ECS metadata requests 
and preserve explicit empty-role direct token URL semantics.
   
   ### Tests
   
   - `cmake --build build-dlf-tdd --target paimon-rest-test -j2`
   - `paimon-rest-test --gtest_filter=Dlf*` (13 tests passed)
   - 31 non-mock REST/DLF regression tests passed
   - `pre-commit run --files <changed files>` (all hooks passed)
   
   The full `unittest` build is blocked on this macOS environment by an 
existing `literal_converter_test.cpp` incompatibility with the SDK 
`INFINITY`/`NAN` macros. The redirect transport regression test compiles, but 
local completion is blocked by the existing macOS `MockRestServer::Stop()` 
accept-thread issue; Linux CI can execute it.
   
   ### API and Format
   
   Adds public `CatalogOptions` keys for DLF REST authentication. No 
storage-format or REST protocol changes.
   
   ### Documentation
   
   Documents the optional OpenSSL build dependency, DLF configuration, 
credential sources, signing algorithms, and refresh behavior.
   
   ### Generative AI tooling
   
   Generated-by: Codex (GPT-5)
   


-- 
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]

Reply via email to