CryoThrust commented on PR #13264:
URL: https://github.com/apache/seatunnel/pull/13264#issuecomment-6906102391

   Thanks @DanielLeens. Updated in `fad348ac10ff457100cb39fe45ede0ca7818a866`:
   
   1. The real-client fixture now uses `Path.toUri()` consistently for the root 
and table base path; no Windows skip or dependency change was added. The new 
[Build](https://github.com/CryoThrust/seatunnel/actions/runs/43795349714) is 
running, so Windows is still pending confirmation.
   2. Authenticated catalog failures reconstruct the declared 
missing/existing-table/database exception types with safe identifiers and no 
raw causes. Other catalog failures carry operation/category context; writer 
action failures use `WRITER_OPERATION_FAILED`, while login/renewal failures 
retain authentication diagnostics. Nested calls preserve sanitized categories. 
Cleanup preserves the first failure and suppresses later sanitized failures. 
Added regression coverage for catalog negative cases and full stack-trace 
sanitization.
   3. Added provider/manager ownership and identity-scope comments, the catalog 
`UnderIdentity` precondition, JVM-global configuration limits, unsupported 
concurrent close/I/O, and the fact that interrupting a waiter does not cancel 
in-flight I/O.
   
   All 37 module tests pass on JDK 11/17, Spotless and the eight-module 
skip-tests verification pass, and the existing Zeta negative-configuration IT 
passes (1 case).
   
   I also ran a separate **real KDC + secure HDFS** harness, without 
login/filesystem/client mocks. It rejects unauthenticated access, enforces 
isolation between two keytab principals, exercises simultaneous protected 
operations, replaces the TGT through forced real keytab re-login, and completes 
INSERT/UPSERT/BULK_INSERT plus DELETE for each principal (six tables, two 
completed commits each). Catalog operations and an unchanged unauthenticated 
global login are checked too. [Sources, reproduction commands and 
results](https://gist.github.com/CryoThrust/96df66d9f8367851c71bee9c4e60f8ed).
   
   The PR description now distinguishes this from positive engine deployment 
coverage. Natural expiry/long-running streaming, secure cached/multi-table 
writers and full engine coverage remain unverified; I am not treating the 
pending Build as green.
   


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