adutra commented on issue #14100: URL: https://github.com/apache/iceberg/issues/14100#issuecomment-3306900680
It seems this issue also affects 1.9.x (please correct me if I'm wrong). This hints indeed at a problem with static fields. In 1.9 we have 2 static fields: * `private static final Cache<Key, SignedComponent> SIGNED_COMPONENT_CACHE` * `static volatile RESTClient httpClient` The cache key takes into account the request URI, so it seems safe to use by different catalogs. The HTTP client however, is initialized with the first catalog's URI and this never changes afterwards: https://github.com/apache/iceberg/blob/4816bf3b5ad68f1c9c2f98c55b56956e9449f178/aws/src/main/java/org/apache/iceberg/aws/s3/signer/S3V4RestSignerClient.java#L142-L146 This doesn't seem safe for use by multiple catalogs sharing the same `S3V4RestSignerClient` instance. I voiced exactly this concern back in March: https://github.com/apache/iceberg/pull/12197#discussion_r1978906243 -- 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: issues-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
