adiranjan25 commented on issue #18943:
URL: https://github.com/apache/iceberg/issues/18943#issuecomment-6888617458

   Hi maintainers,
   
   I've completed a local reproduction and investigated the Lake Formation 
initialization path.
   
   **Regression confirmed:** On `origin/main` (`234d55774`), enabling 
`s3.preload-client-enabled` results in zero S3 clients being created during 
`S3FileIO.initialize()`, although the expected count is one. The default 
lazy-initialization test passes.
   
   **Compatibility finding:** `LakeFormationAwsClientFactory.s3()` performs a 
Glue `GetTable` lookup. Although `GlueTableOperations.doCommit()` creates a 
temporary Glue table for new-table operations, FileIO may be initialized 
earlier through `GlueTableOperations.io()`.
   
   Therefore, restoring eager initialization unconditionally could reintroduce 
the missing-table failures reported previously.
   
   Would you prefer:
   
   1. Restoring eager initialization with explicit safeguards for Lake 
Formation table creation; or
   2. Deprecating `s3.preload-client-enabled` and removing its use from 
`GlueCatalog`?
   
   I have the regression tests ready and can proceed with the preferred 
approach.
   
   Thanks!


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to